From: R.E.Wolff@BitWizard.nl (Rogier Wolff)
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Keith Owens <kaos@ocs.com.au>,
louisg00@bellsouth.net, linux-kernel@vger.kernel.org,
device@lanana.org
Subject: Re: Unknown error
Date: Sun, 12 Aug 2001 21:55:45 +0200 (MEST) [thread overview]
Message-ID: <200108121955.VAA25314@cave.bitwizard.nl> (raw)
In-Reply-To: <E15Vti5-0005ao-00@the-village.bc.nu> from Alan Cox at "Aug 12, 2001 12:47:13 pm"
Alan Cox wrote:
> > 2.4.8 says that device 228 is unassigned, but ...
> >
> > drivers/char/drm/drm.h:#define DRM_MAJOR 226
> > drivers/net/wan/sdla_chdlc.c:#define WAN_TTY_MAJOR 226
> >
> > Somebody has been naughty and used a code not assigned to them.
> 226 char Direct Rendering Infrastructure (DRI)
> 0 = /dev/dri/card0 First graphics card
> 1 = /dev/dri/card1 Second graphics card
>
>
> Peter - was this dual issued, or do Sangoma need to be spanked. The obvious
> place to put the sdla tty would I think be 229, since its not physically
> possible to put one in an iSeries machine.
Speaking of which...
I always (try to) write my drivers to do:
#ifndef MY_MAJOR
#define MY_MAJOR xyz
#endif
This allows "test-compilation" with -Dtest_major , but is also
preparing for having a "majors.h" which defines ALL the major numbers
in one place. The place where it /completly/ obvious if two devices
are trying to use the same major....
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* There are old pilots, and there are bold pilots.
* There are also old, bald pilots.
prev parent reply other threads:[~2001-08-13 7:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-12 5:40 Unknown error louisg00
2001-08-12 7:36 ` Keith Owens
2001-08-12 11:47 ` Alan Cox
2001-08-12 19:40 ` H. Peter Anvin
2001-08-12 19:55 ` Rogier Wolff [this message]
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=200108121955.VAA25314@cave.bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=device@lanana.org \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=louisg00@bellsouth.net \
/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