I just responded to the other post, and I definitely agree with you that when you're working with so many systems, knowing you have a baseline for the power supplies is important! (Especially given how sketchy those third-party adapters can be...)
But I will say I think it's pretty anti -consumer, and not accidental at all, that there is vendor lock in there. And as I said in that reply, I think a setting in the BIOS with a warning (and maybe a warranty invalidation?) that allowed it would have been the more friendly approach, but I can only imagine how much the lawyers would yell about why that's a bad idea, haha
USB-PD made me so happy, I was using my Apple power adapter with my Surface and Dell laptops and it was great!
As a person who has worked at Dell as a firmware engineer, with the very same 1-wire connection over that third data pin.
Yes, it's true that at least HP and Dell will only allow use of an "authentic" adapter. The internal reasoning for this is that third party adapters may SAY they are compatible with system voltage/current, but in reality it might be insufficient or damage the board. (I personally think this is not a good enough reason, and that a BIOS setting with a safety disclaimer would be enough, but I digress)
The second and much more legitimate reason is that yes the adapter reports to the system what voltage/current it supports, so the system can set it's charging and power targets accordingly (e.g. if wattage is too low, the system will know to pull from the battery a well)
This data connection is proprietary for these three pin connectors (there's just not a standard, and no one wanted to negotiate one), so they just don't work between different companies. And this "accidentally" works as a vendor lock (I say accidentally because internally we always talk about it as if we are providing a safe service for customers, but I know the reality of capital so...)
What I said is true of Dell, and to my understanding it's also true of HP (as they both constantly try to copy each other, good and bad). So yes, both things are true at once.. it is in fact a design that is useful for these pre-usbpd systems, and very "conveniently" it has allowed vendors to lock in their adapters
That said, my understanding is that it's pretty easy to get a third party adapter that intentionally mimics that data pin, and they're much cheaper than the oem versions but of course buyer beware (personally, I've been horrified, completely horrified, at what I've seen on the insides of various cheap power adapters 😅)
Wow, I don't often come across other folks with both similar limitations and curiosity! (Except a reversal on the potato vs oatmeal textures)
Especially the onion thing, it's crazy the gag reflex can be so strong, or that we can tell so easily that onion has once touched something. I find shallots particularly unbearable! (Though I do get sad because while I can't stand onions, I can also taste the notes I assume most people can, and can tell how good they would be in certain contexts, like a perfect burger or as a bbq side. I want to know what that experience is like 😰)
You monster! Now I'm having UCHI, OHCI, and EHCI flashbacks, how finicky those first keyboards were, and the bios emulation layer used to make them seem like a normal PS/2 keyboard.
As a former legacy BIOS and UEFI developer, who has also done a ton of basic IT support... thank you, I am now having traumatic flashbacks (and I even had access to the firmware code! But that's not always enough... Never enough.)
These days I can't even very leftover prototypes to use, dang.
I think you might need to use the MODE command to set the COM port up prior to use.
Also I'm less sure about this part, but I think CTTY is only useful if you are using the pi as the user terminal (since I think it stops DOS from using the screen/keyboard and redirects that to/from the serial port)? I don't know what programs come on that supplemental disk, but depending on your comfort level, you could create a simple terminal emulator with a batch file, debug.exe, or potentially basic (if that's included). In a pinch, you might also be able to copy an ascii file from the pi to the luggable over the com port (copy.exe COM1 localfile)/(cat remotefile > /dev/ttyS0). You could also encode a binary file as base64 and then use a simple basic program to decode it?
For reference, I'm just a few years older than this thing 😁 and maybe my old brain is misremembering things...
What's the difference between a chicken burger and a chicken sandwich? (I'm developing a theory that British folks will generally say the difference is the bun/bread and American folks will generally say whole chicken vs ground chicken...)
Oh great that's helpful, thank you!
Also... I said what I said 😁
ls or Is (or 1s)?
The depth of your work continues to astound, thank you for the inspiration!
It looks just like mine too, and the thought of washing that thing is just "oh no"
(But it is definitely comfy to sleep under!)
Yep, Lunar Legend (GBA)! I haven't played this one or the original, but I've been on a jrpg kick lately.
thank you for getting carried away! (hopefully not by birds!)
quite the imp, aren't you?
hope we all win but i guess we gotta wait and see 😁
I just responded to the other post, and I definitely agree with you that when you're working with so many systems, knowing you have a baseline for the power supplies is important! (Especially given how sketchy those third-party adapters can be...)
But I will say I think it's pretty anti -consumer, and not accidental at all, that there is vendor lock in there. And as I said in that reply, I think a setting in the BIOS with a warning (and maybe a warranty invalidation?) that allowed it would have been the more friendly approach, but I can only imagine how much the lawyers would yell about why that's a bad idea, haha
USB-PD made me so happy, I was using my Apple power adapter with my Surface and Dell laptops and it was great!
As a person who has worked at Dell as a firmware engineer, with the very same 1-wire connection over that third data pin.
Yes, it's true that at least HP and Dell will only allow use of an "authentic" adapter. The internal reasoning for this is that third party adapters may SAY they are compatible with system voltage/current, but in reality it might be insufficient or damage the board. (I personally think this is not a good enough reason, and that a BIOS setting with a safety disclaimer would be enough, but I digress)
The second and much more legitimate reason is that yes the adapter reports to the system what voltage/current it supports, so the system can set it's charging and power targets accordingly (e.g. if wattage is too low, the system will know to pull from the battery a well) This data connection is proprietary for these three pin connectors (there's just not a standard, and no one wanted to negotiate one), so they just don't work between different companies. And this "accidentally" works as a vendor lock (I say accidentally because internally we always talk about it as if we are providing a safe service for customers, but I know the reality of capital so...)
What I said is true of Dell, and to my understanding it's also true of HP (as they both constantly try to copy each other, good and bad). So yes, both things are true at once.. it is in fact a design that is useful for these pre-usbpd systems, and very "conveniently" it has allowed vendors to lock in their adapters
That said, my understanding is that it's pretty easy to get a third party adapter that intentionally mimics that data pin, and they're much cheaper than the oem versions but of course buyer beware (personally, I've been horrified, completely horrified, at what I've seen on the insides of various cheap power adapters 😅)
Wow, I don't often come across other folks with both similar limitations and curiosity! (Except a reversal on the potato vs oatmeal textures)
Especially the onion thing, it's crazy the gag reflex can be so strong, or that we can tell so easily that onion has once touched something. I find shallots particularly unbearable! (Though I do get sad because while I can't stand onions, I can also taste the notes I assume most people can, and can tell how good they would be in certain contexts, like a perfect burger or as a bbq side. I want to know what that experience is like 😰)
As another person from the southeast, similar is true down here and most places: a locally known and mildly sketchy situation is the best! (Usually..)
Gas station places with a packed parking lot, open church bbqs, the smoky old dark wood panel places serving the best burger you ever had.
That said, the first time I had a proper tamale when I moved to Texas, omgosh! Magic.
You monster! Now I'm having UCHI, OHCI, and EHCI flashbacks, how finicky those first keyboards were, and the bios emulation layer used to make them seem like a normal PS/2 keyboard.
Why???
As a former legacy BIOS and UEFI developer, who has also done a ton of basic IT support... thank you, I am now having traumatic flashbacks (and I even had access to the firmware code! But that's not always enough... Never enough.)
These days I can't even very leftover prototypes to use, dang.
It took me way way way too long to figure out what y'all were talking about, I was legit worried about a new STI. I need to get out more...
I payed it (almost in blood) literally the first day I moved there 😅
Awww what an absolute (and hungry) cutie! 😍
Would you want it any other way??
Aw, that reminds me of a childhood book The Little Mouse, The Red Ripe Strawberry, and the Big Hungry Wolf.
Thank you for the smile!
Oh that's cool it came with an XT-IDE controller, I don't think the dual floppy models came with one stock, will definitely save ya some hassle.
I think you're right, trying to get the storage working would be less painful than a serial link bootstrap. Will cross my fingers for ya!
I think you might need to use the MODE command to set the COM port up prior to use.
Also I'm less sure about this part, but I think CTTY is only useful if you are using the pi as the user terminal (since I think it stops DOS from using the screen/keyboard and redirects that to/from the serial port)? I don't know what programs come on that supplemental disk, but depending on your comfort level, you could create a simple terminal emulator with a batch file, debug.exe, or potentially basic (if that's included). In a pinch, you might also be able to copy an ascii file from the pi to the luggable over the com port (copy.exe COM1 localfile)/(cat remotefile > /dev/ttyS0). You could also encode a binary file as base64 and then use a simple basic program to decode it?
For reference, I'm just a few years older than this thing 😁 and maybe my old brain is misremembering things...
What's the difference between a chicken burger and a chicken sandwich? (I'm developing a theory that British folks will generally say the difference is the bun/bread and American folks will generally say whole chicken vs ground chicken...)
Edit: also, nice sandwich!