lkml.org 
[lkml]   [2002]   [Jan]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Serial Driver Name Question (kernels 2.4.x)

Andrew Morton wrote:
>
> Well, with the scheme I proposed most drivers won't need the
> ifdef. It'll just be:
>
> serial_driver.name = "cua";
>
> With devfs enabled that expands to cua/42. Without devfs it expands
> to cua42.

Check my previous msg. Actually that won't work for other drivers
other than serial.c, that's why we should use the scheme I suggested
on that msg.

Hmmmm, I just thought about something that might be a problem with
this change. I believe Richard Gooch is the right person to tell us
whether this is a problem or not.

We're just talking about print msgs in tty_io.c (and the scheme I
suggested -- i.e. to use 'tts/X' for devfs and 'ttyX' for non-devfs
and have "%s%d" in tty_io.c's printk call -- does cover all driver in
that aspect), but I'm not sure whether devfs uses the driver.name
definition for something else. If that's the case, then devfs would
need to be updated as well to comply with the new driver.name
definition.

Richard, is this a problem or not?!?!

Later,
--
Ivan Passos -o)
Integration Manager, Cyclades - http://www.cyclades.com /\\
Project Leader, NetLinOS - http://www.netlinos.org _\_V
--------------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:15    [W:0.179 / U:3.040 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site