[<prev] [next>] [day] [month] [year] [list]
Message-ID: <163517.42504.qm@web26203.mail.ukl.yahoo.com>
Date: Sat, 20 Sep 2008 10:51:24 +0000 (GMT)
From: Michael Trimarchi <trimarchimichael@...oo.it>
To: chri <chripell@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>
Cc: linux-kernel@...r.kernel.org, linux-serial@...r.kernel.org
Subject: Re: [PATCH] max3100 driver
Hi,
----- Messaggio originale -----
> Da: chri <chripell@...il.com>
> A: Andrew Morton <akpm@...ux-foundation.org>
> Cc: linux-kernel@...r.kernel.org; linux-serial@...r.kernel.org
> Inviato: Sabato 20 settembre 2008, 12:35:26
> Oggetto: Re: [PATCH] max3100 driver
>
> Sorry, sent HTML mail by mistake, so resending :-/
>
>
> On Sat, Sep 20, 2008 at 10:24 AM, Andrew Morton
> wrote:
>
> > > +#define MAX3100_MAJOR 204
> >
> > Allocating a new major is a Big Deal. It involves getting the major
> > registered by contacting device@...ana.org.
> >
> > It's better to dynamically allocate it - let udev handle it.
> >
>
>
> I looked at other serial driver as an example and checked devices.txt:
> if I don't get it wrong major 204 should be already reserved for
> serial port. Anyway I choose a minor number already allocated by
> mistake (did not see the "...") and will correct that. Is this ok or I
> *have to* move to dynamic major (it's a bit a nuisance since max3100
> is used in embedded system where udev is not always used)?
>
Well, a solution can be to use dynamic allocation if is not specified in
the platform data of the device, so you can statically allocated for
embedded device. So if you don't set the major, the tty layer find one
for you.
Regards Michael
__________________________________________________
Do You Yahoo!?
Poco spazio e tanto spam? Yahoo! Mail ti protegge dallo spam e ti da tanto spazio gratuito per i tuoi file e i messaggi
http://mail.yahoo.it
--
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