[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201001231432.09918.isdn@linux-pingi.de>
Date: Sat, 23 Jan 2010 14:32:09 +0100
From: Karsten Keil <isdn@...ux-pingi.de>
To: Marcel Holtmann <marcel@...tmann.org>
Cc: Alan Cox <alan@...rguk.ukuu.org.uk>,
Jan Kiszka <jan.kiszka@....de>,
David Miller <davem@...emloft.net>,
linux-kernel@...r.kernel.org, i4ldeveloper@...tserv.isdn4linux.de,
isdn4linux@...tserv.isdn4linux.de, netdev@...r.kernel.org,
Alan Cox <alan@...ux.intel.com>
Subject: Re: [PATCH 31/31] CAPI: Officially claim char major 191
On Samstag, 23. Januar 2010 13:48:12 Marcel Holtmann wrote:
> Hi Alan,
>
> > > I found no trace of this mysterious "pcl181" device, neither in-tree
> > > nor out there in the wild. At the same time, the in-tree CAPI
> > > middleware is using major 191 for many years now and obviously without
> > > any conflict. Let's officially claim this major number.
> >
> > This is not the way it should have been done but whoever needs spanking
> > got away with it years ago. Given that this seems the best way forward.
> >
> > With LANANA hat on
>
> actually in the days of udev, the capifs is not really needed anymore.
> The right choice would be to remove it. I haven't been enabling it since
> years.
>
So far I understand, the pppd capiplugin is the only user of it, so it could
be disabled for most users without any problems, as long they are not using
PPP connections via CAPI.
I never understand capifs very well, I think that it can be dropped because of
udev, but maybe need some adjustment in user space as well (make sure that
udev did create the node before open it).
I f I remember correctly, here was some proposal to replace the /dev/capi/
nodes with devpts, this would remove the complete capi_tty device major
as well.
Karsten
--
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