On Tue, Apr 02, 2002 at 09:51:49PM -0800, Stuart Lynne wrote:
> On Tue, Apr 02, 2002 at 09:12:25PM -0800, Greg KH wrote:
> > On Tue, Apr 02, 2002 at 02:29:01PM -0800, David Brownell wrote:
> >
> > I can create a linux-usb-devices list on linux-usb.org if Stuart doesn't
> > mind. Might as well ke
On Tue, Apr 02, 2002 at 02:35:52PM -0800, Stuart Lynne wrote:
> On Tue, Apr 02, 2002 at 02:29:01PM -0800, David Brownell wrote:
> > > The arm port has a USB host and client driver (or so I've been told, the
> > > client might be this one for all I know :) I've seen the host driver,
> > > and it w
On Wednesday 03 April 2002 01:21, Alan Cox wrote:
> > So all things being equal, bus was shorter than peripheral, in common
> > use, and seemed to allow us to consider them as separate entities.
>
> Wouldn't longer names be clearer. Disk space is cheap 8)
>
> controllers/
> devices/
>
On Tue, Apr 02, 2002 at 09:12:25PM -0800, Greg KH wrote:
> On Tue, Apr 02, 2002 at 02:29:01PM -0800, David Brownell wrote:
>
> I can create a linux-usb-devices list on linux-usb.org if Stuart doesn't
> mind. Might as well keep all of the relevant lists in the same place :)
Sure or we can leave
On Tue, Apr 02, 2002 at 01:56:21PM -0800, Stuart Lynne wrote:
> > - can I add the safe_serial driver to the tree? I have had some
> > people ask me about something like this in the past, thanks
> > for writing it.
>
> Yes.
I added the safe_serial driver to the existing 2.5 tree,
On Tue, Apr 02, 2002 at 02:29:01PM -0800, David Brownell wrote:
> > The arm port has a USB host and client driver (or so I've been told, the
> > client might be this one for all I know :) I've seen the host driver,
> > and it will probably end up in the drivers/usb/ directory soon. Same
> > thin
On Tue, Apr 02, 2002 at 07:56:40PM -0800, Mark McClelland wrote:
> Greg KH wrote:
>
> >I think the network and video drivers now have a critical mass to move
> >them to their own directory if no one objects. Nice thing about
> >bitkeeper, file moves are very simple to do :)
> >
>
> Should they
Greg KH wrote:
>I think the network and video drivers now have a critical mass to move
>them to their own directory if no one objects. Nice thing about
>bitkeeper, file moves are very simple to do :)
>
Should they be moved to drivers/net and drivers/media/video instead? I
mean, no one would th
On Tue, Apr 02, 2002 at 05:24:53PM -0800, David Brownell wrote:
> > > > drivers/usb/bi device interfaces
> > >
> > > "bi"? Why not "di"?
> >
> > ...
> > You would also end up describing them as Linux USB Device device drivers
> > which is starting to get silly :-)
>
> Which is why I've talked
> > > drivers/usb/bi device interfaces
> >
> > "bi"? Why not "di"?
>
> ...
> You would also end up describing them as Linux USB Device device drivers
> which is starting to get silly :-)
Which is why I've talked about "Device Controller Drivers", by
analogy to their corresponding "Host Control
> > Different terminology for the same thing would just be
> > confusing, for example... a USB "interface" should be
> > called the same thing everywhere, but seems like it's
> > become a "function" in this USBD code, while the
> > word "interface" is used to describe controllers
> > (host and dev
> > Wouldn't longer names be clearer. Disk space is cheap 8)
> >
> > controllers/
> > devices/
> > filesystem/
> > core/
>
> Sure ... but there are two types of bus controllers, host side
> and device side. For the moment I'd stick with keeping
> all the host controller drivers in the "hcd" di
> > So all things being equal, bus was shorter than peripheral, in common
> > use, and seemed to allow us to consider them as separate entities.
>
> Wouldn't longer names be clearer. Disk space is cheap 8)
>
> controllers/
> devices/
> filesystem/
> core/
Sure ... but there are two types of bus
> So all things being equal, bus was shorter than peripheral, in common
> use, and seemed to allow us to consider them as separate entities.
Wouldn't longer names be clearer. Disk space is cheap 8)
controllers/
devices/
filesystem/
core/
?
__
On Tue, Apr 02, 2002 at 02:29:01PM -0800, David Brownell wrote:
> > The arm port has a USB host and client driver (or so I've been told, the
> > client might be this one for all I know :) I've seen the host driver,
> > and it will probably end up in the drivers/usb/ directory soon. Same
> > thin
On Tue, Apr 02, 2002 at 02:06:37PM -0800, Greg KH wrote:
> > On the other hand re-organizing everything into one tree like:
> >
> > drivers/usb/bi device interfaces
>
> "bi"? Why not "di"?
Hardware manufacturers seem to refer to these chips most often with
terms like:
US
> The arm port has a USB host and client driver (or so I've been told, the
> client might be this one for all I know :) I've seen the host driver,
> and it will probably end up in the drivers/usb/ directory soon. Same
> thing goes for a embedded PPC USB host controller driver that is based
> off
On Tue, Apr 02, 2002 at 10:40:08AM -0800, David Brownell wrote:
> > - do you want me to add this to the main kernel tree? It should
> > probably go somewhere like drivers/usb/device.
>
> Well, parts of it. I had half thought about drivers/usb/dcd
> for the Device Controller Driver parts (matc
On Tue, Apr 02, 2002 at 10:40:08AM -0800, David Brownell wrote:
> > - do you want me to add this to the main kernel tree? It should
> > probably go somewhere like drivers/usb/device.
> Before it goes there, I thought I'd request some discussion
> and convergence of the API with what's alrea
On Tue, Apr 02, 2002 at 01:56:21PM -0800, Stuart Lynne wrote:
> On Tue, Apr 02, 2002 at 09:25:17AM -0800, Greg KH wrote:
> > On Mon, Apr 01, 2002 at 11:32:25PM -0800, Stuart Lynne wrote:
> > > The Linux USB Device software developed by Lineo, currently being used
> > > by Sharp for the Zaurus, has
On Tue, Apr 02, 2002 at 09:25:17AM -0800, Greg KH wrote:
> On Mon, Apr 01, 2002 at 11:32:25PM -0800, Stuart Lynne wrote:
> > The Linux USB Device software developed by Lineo, currently being used
> > by Sharp for the Zaurus, has been released under a GPL license and is
> > available at:
>
> Yeah!
> - do you want me to add this to the main kernel tree? It should
> probably go somewhere like drivers/usb/device.
Well, parts of it. I had half thought about drivers/usb/dcd
for the Device Controller Driver parts (matching 'hcd' for
the Host Controller Drivers :), but some of those would
bes
On Mon, Apr 01, 2002 at 11:32:25PM -0800, Stuart Lynne wrote:
> The Linux USB Device software developed by Lineo, currently being used
> by Sharp for the Zaurus, has been released under a GPL license and is
> available at:
Yeah! Thanks for releasing this code, I am very happy to see it.
A few q
On Tue, Apr 02, 2002 at 06:14:52PM +1000, Brad Hards wrote:
> On Tue, 2 Apr 2002 17:32, Stuart Lynne wrote:
>
> > The network and serial drivers have optional CRC checking across all
> > bulk transfers (to compensate for problems with StrongARM and Linkup
> > FIFO implementations).
> I am not sur
The Linux USB Device software developed by Lineo, currently being used
by Sharp for the Zaurus, has been released under a GPL license and is
available at:
http://oss.lineo.com/usb/
This stack is similiar in design to the linux host USB software but
tailored to the requirements for the de
25 matches
Mail list logo
