On Mon, Jan 20, 2003 at 08:14:23PM +0100, Oliver Neukum wrote:
> Am Montag, 20. Januar 2003 19:21 schrieb David Brownell:
> >
> > - Someone just emailed me for help on that classic, and still
> > unresolved, issue of associating a device from 'lsusb' (etc)
> > with the right /dev/... prin
Tyson D Sawyer wrote:
Though I'm not real useful when it comes to contributing code at this
time, I'd like to add my voice to those that feel the lack of decent
topological names has real user impact and limits usability.
For us it isn't printers, but rather serial ports.
Just for the record,
Alan Stern wrote:
What is the cause of all these problems relating to device resetting and
probing?
IMO the root cause was an assumption that there'd be only one
config, or at least only one usable. There are a number of
assumptions inside usbcore which turn up trouble when changing
device con
Am Dienstag, 21. Januar 2003 21:19 schrieb Alan Stern:
> On Mon, 20 Jan 2003, David Brownell wrote:
> > Oliver Neukum wrote:
> > > So here's the list of things related to the core I remember so we can
> > > look at the issues and see which need attention before 2.6.0
> > >
> > > - reseting during p
On Mon, 20 Jan 2003, David Brownell wrote:
> Oliver Neukum wrote:
>
> > So here's the list of things related to the core I remember so we can look
> > at the issues and see which need attention before 2.6.0
> >
> > - reseting during probe will deadlock
> > - reseting through usbfs will not repro
Am Dienstag, 21. Januar 2003 02:19 schrieb David Brownell:
> Oliver Neukum wrote:
> > When will we go to code freeze?
>
> No such thing as "code freeze", not like commercial UNIX
> where it means a year before customers could see fixes.
> (If they're willing to pay through the nose for patches.)
M
Oliver Neukum wrote:
When will we go to code freeze?
No such thing as "code freeze", not like commercial UNIX
where it means a year before customers could see fixes.
(If they're willing to pay through the nose for patches.)
On the other hand, 2.5.59 won't change for a few weeks,
that's at leas
Am Montag, 20. Januar 2003 21:41 schrieb David Brownell:
> Oliver Neukum wrote:
> >>>Removals? Additions? Comments?
> >>
> >>Yes, I'll be glad to see more of the usbcore cleanups happen.
> >>Here are a random bunch of things
> >>
> >> - Someone just emailed me for help on that classic, and still
>
David Brownell wrote:
Oliver Neukum wrote:
Removals? Additions? Comments?
Yes, I'll be glad to see more of the usbcore cleanups happen.
Here are a random bunch of things
- Someone just emailed me for help on that classic, and still
unresolved, issue of associating a device from 'lsusb' (
Oliver Neukum wrote:
Removals? Additions? Comments?
Yes, I'll be glad to see more of the usbcore cleanups happen.
Here are a random bunch of things
- Someone just emailed me for help on that classic, and still
unresolved, issue of associating a device from 'lsusb' (etc)
with the right /
Am Montag, 20. Januar 2003 19:21 schrieb David Brownell:
> Oliver Neukum wrote:
> > Hi,
> >
> > I was just looking at the TODO list and it seemed to me that a list
> > somewhat more specific and focused on usbcore might be useful.
>
> I think the real issue is who will fix the various bugs and issu
Oliver Neukum wrote:
Hi,
I was just looking at the TODO list and it seemed to me that a list somewhat
more specific and focused on usbcore might be useful.
I think the real issue is who will fix the various bugs and issues that
turn up, but having lists can help focus that energy.
So here's
Hi,
I was just looking at the TODO list and it seemed to me that a list somewhat
more specific and focused on usbcore might be useful.
So here's the list of things related to the core I remember so we can look
at the issues and see which need attention before 2.6.0
- reseting during probe will d
13 matches
Mail list logo