[GreenKeys] Interface ASR33 to Linux serial port

Chris Elmquist chrise at pobox.com
Tue Jan 9 16:29:19 EST 2024


On Wednesday (01/10/2024 at 06:57AM +1100), Dave Horsfall wrote:
> On Tue, 9 Jan 2024, Chuck Rehor wrote:
> 
> > [...] With the RPi running its version of Linux, I’ve scratched my head 
> > trying to get gettys to run right because it might show the login 
> > prompt, but either not accept characters, or it accepts characters but 
> > would not give me a Password prompt, so I couldn't get logged in. 
> > Searching on the internet, I saw other people had problems with the 
> > Linux drivers too.
> 
> I'm surprised that Linux went down the same path of sabotaging systems it 
> doesn't approve of as did M$; who knows what other damage was caused in 
> the process, if you innocently used a fake chip?

Actually, I think that was the Windows FTDI driver doing the sabotaging.
They too were burned by the chip ripoffs so made an attempt to "get even".
If the Windows FTDI driver detected a non-FTDI chip, it would refuse to
enumerate it and that port was not useable from Windows.

However the open-source FTDI driver, which most people use in their Linux
kernel, did not do this evil bad thing.  Therefore, your counterfeit
yet functional FTDI-like port will still work in Linux.

This is extremely common in these programming cables for various ham
radios--  the TYT and clones in particular.

> My brother gave me one of those cables which doesn't work on his Windoze 
> box, yet runs just fine on my FreeBSD server...

Yup and it will with Linux too.

So, how are you guys getting your Linux with 110 baud interfaces to
handle uppercase only TTYs?

I played with this a couple years ago and failed because it seemed like
all the IOCTLs in the kernel, and "stty" and "getty" options relating
to uppercase had been deprecated.  I could not get there with a modern
distribution.  Have they put those goodies back?

Chris
-- 
Chris Elmquist NØJCF



More information about the GreenKeys mailing list