Re: Allow 8250 to work on sparc.

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Mark Fortescue
Date: Tuesday, September 16, 2008 - 6:15 am

Hi Alan,

On Tue, 16 Sep 2008, Alan Cox wrote:


At the driver level there are lots of varients but I was under the 
impression that at the user level, the interface is common for async 
serial ports.

Latency can be an issue, but can it be read/changed via the user <-> 
kernel interface in a way that is not common to all async serial ports?

If not, it is transparent at the programming interface for user level code 
so the USB serial ports are no different at this level to classic PC AT 
serial ports and as such I see no reason why, in the long run, they should 
not share minor number space.

Taking the argument to its logical conclusion, all devices that have a 
common user <-> kernel interface should have device drivers that are 
capable of sharing minor device number space.

I am sure this discusion will crop up again in the future :).

Regards
 	Mark.
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[PATCH 0/2]: Allow 8250 to work on sparc., David Miller, (Fri Sep 12, 9:18 pm)
Re: Allow 8250 to work on sparc., Mark Fortescue, (Mon Sep 15, 7:26 am)
Re: Allow 8250 to work on sparc., Alan Cox, (Mon Sep 15, 9:22 am)
Re: Allow 8250 to work on sparc., Mark Fortescue, (Mon Sep 15, 11:51 am)
Re: Allow 8250 to work on sparc., David Miller, (Mon Sep 15, 11:51 am)
Re: Allow 8250 to work on sparc., Alan Cox, (Tue Sep 16, 3:54 am)
Re: Allow 8250 to work on sparc., Mark Fortescue, (Tue Sep 16, 6:15 am)