[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1339056804.4964.8.camel@wall-e>
Date: Thu, 07 Jun 2012 10:13:24 +0200
From: Stefani Seibold <stefani@...bold.net>
To: Alan Stern <stern@...land.harvard.edu>
Cc: linux-kernel@...r.kernel.org, gregkh@...uxfoundation.org,
oneukum@...e.de, alan@...rguk.ukuu.org.uk,
linux-usb@...r.kernel.org
Subject: Re: [PATCH] fix usb skeleton driver
Am Mittwoch, den 06.06.2012, 16:22 -0400 schrieb Alan Stern:
> On Wed, 6 Jun 2012, Stefani Seibold wrote:
>
> > The reason to fix the skeleton driver was about the complains for my
> > NRPZ driver, which was based on the design of the usb skeleton driver.
> >
> > > Going even farther, I'm not so sure it's a good idea for usb-skeleton
> > > to try supporting both synchronous and asynchronous accesses. This
> > > adds a layer of complexity that people just don't need. IMO it would
> > > be better to have two separate example drivers, an easy one that is
> > > purely synchronous and a more advanced one that is purely async.
> > >
> >
> > Agree, i think this would be a good idea to have to separate drivers.
> > Both should be also working drivers, for really simple hardware.
> >
> > The best way for me to do this is to shrink later this to a simplified
> > driver.
>
> That makes sense. Will you do it?
Yes, if nobody other will do this.
>
> > I think it is important to have a clean and working example. It would
> > save a lot of time for everybody and shrinks the number of round trips.
>
> How can you tell that it works? By testing your NRPZ driver?
>
That is an option. But i will look for a more generic hardware. Maybe a
smartphone or a usb pen drive.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists