From: "Marc - A. Dahlhaus" <mad@wol.de>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org, isdn@linux-pingi.de
Subject: Re: [PATCH] Fix capi devicenames
Date: Fri, 01 Oct 2010 10:36:32 +0200 [thread overview]
Message-ID: <1285922192.13411.53.camel@marc> (raw)
In-Reply-To: <AANLkTimRa9VsOgSkcdrg=41pskEbMhNL4D9SXeV3dztG@mail.gmail.com>
Am Donnerstag, den 30.09.2010, 21:20 +0200 schrieb Kay Sievers:
--8<--
>
> devices.txt is just bogus in this case and states stuff which was
> never used in the real world. But you don't need to touch it. Just add
> the naming hints (char *(*devnode)) to the capi class and nothing will
> change, the device names in /sys and everywhere else will stay as they
> are today, just devtmpfs and udev will create the right device nodes
> out of the kernel supplied additional information. We did this for the
> rest of the kernel the same way.
Hello Kay,
for the capi tty, if not mistaken, it looks like i need to add a
dev->devnode = 'capi/';
line but i have no clue what it needs to change the capi_class.
Looks like a larger rework of the code in capi.c to me.
It would collide in the kernel if i fix the typo for the control device
but don't change the tty device name by the same time.
(20th capi application tty would become capi20 under sysfs)
So i took the approach to ignore the devices.txt in the v2 patch and
just fix the control device node to conform to the spec and also fix the
tty node names to the ones of capifs that superseded the manualy created
tty device nodes mentioned in devices.txt
Hope this is more appropriate than my first patch.
Is there a documentation that could guide me in how to fix it in the way
you suggested, if the v2 patch also gets naked?
thanks,
Marc
next prev parent reply other threads:[~2010-10-01 8:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 19:21 [PATCH] Fix capi devicenames Marc - A. Dahlhaus
2010-09-30 9:30 ` Alan Cox
2010-09-30 10:08 ` Kay Sievers
2010-09-30 10:56 ` Alan Cox
2010-09-30 10:37 ` Marc - A. Dahlhaus
2010-09-30 10:50 ` Kay Sievers
2010-09-30 11:29 ` Alan Cox
2010-09-30 12:50 ` Marc - A. Dahlhaus
2010-09-30 17:35 ` Olivier Galibert
2010-09-30 19:20 ` Kay Sievers
2010-10-01 8:02 ` [PATCH] Fix capi devicenames v2 Marc - A. Dahlhaus
2010-10-01 8:36 ` Marc - A. Dahlhaus [this message]
2010-10-01 9:20 ` [PATCH] Fix capi devicenames Kay Sievers
2010-09-30 11:35 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1285922192.13411.53.camel@marc \
--to=mad@wol.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=isdn@linux-pingi.de \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox