Hrm... I'm having some trouble envisioning exactly what you would be
doing, and how it would affect what I see in my logs...
How about you go ahead and make a prototype, then run it by the
maintainers on an individual basis. Whoever wants it can then take it.
I'm at least interested in seeing what you have in mind.
Matt Dharm
On Mon, 27 Mar 2000, Greg KH wrote:
> On Mon, Mar 27, 2000 at 11:01:06PM -0800, Matthew Dharm wrote:
> > The problem with this idea is that some debugging will drown out other
> > debugging. For instance, you can't turn on usb mass storage debugging
> > with HCD debugging -- if you do that, none of the mass storage debugging
> > messages will get through.
> >
>
> I agree. That's why I think that the general debugging message that all
> the drivers spit out should be controlled by the CONFIG_USB_DEBUG
> option. If a user turns this on, then they should get enough debug
> messages outputted that they could then forward to the developer or the
> list. Or if they just want to see more of what is going on with their
> USB devices. That's what I did for usbcore.
>
> Then, if the driver wants to have a TON of debug messages, have that be
> a separate configuration item. Or leave it buried in the code for
> developers only. Either way is fine with me, but for either way, a patch
> needs to be made. And I'm volunteering, but I will only do it if the
> maintainers don't mind (maybe I should just submit the changes to the
> different maintainers...)
>
> greg k-h
>
--
Matthew Dharm Home: [EMAIL PROTECTED]
Engineer, Qualcomm, Inc. Work: [EMAIL PROTECTED]
Somebody call an exorcist!
-- Dust Puppy
User Friendly, 5/16/1998
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
