[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4703D5B9.8050808@hartkopp.net>
Date: Wed, 03 Oct 2007 19:47:37 +0200
From: Oliver Hartkopp <oliver@...tkopp.net>
To: David Miller <davem@...emloft.net>, shemminger@...ux-foundation.org
CC: acme@...stprotocols.net, urs@...ogud.escape.de,
netdev@...r.kernel.org, kaber@...sh.net, tglx@...utronix.de,
yoshfuji@...ux-ipv6.org, ebiederm@...ssion.com,
oliver.hartkopp@...kswagen.de, urs.thuermann@...kswagen.de
Subject: Re: [PATCH 5/7] CAN: Add virtual CAN netdevice driver
David Miller wrote:
> From: Stephen Hemminger <shemminger@...ux-foundation.org>
> Date: Tue, 2 Oct 2007 14:52:36 -0700
>
>
>> Please consider using netif_msg_xxx() and module parameter to set
>> default message level, like other real network drivers already do.
>>
>
> I keep seeing this recommendation, but the two supposedly most mature
> and actively used drivers in the tree, tg3 and e1000 and e1000e, all
> do not use this scheme.
>
> In fact there are tons of drivers that even hook up the ethtool
> msg_level setting function and never even use the value.
>
> If people aren't using netif_msg_xxx() and the ethtool msg_level
> facilities properly, it's because there is a severe dearth of good
> example drivers to learn about it from.
>
The currently available CAN netdevice drivers do not have a common debug
concept neither any runtime control mechanism for this debugging. So
netif_msg_xxx() is definitely worth to look at instead of creating any
new stuff in this direction, before posting any 'real' CAN network
driver here.
Thanks very much for that hint!
Oliver
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists