From: Hubert Mantel <mantel@suse.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linus Torvalds <torvalds@transmeta.com>,
"H. Peter Anvin" <device@lanana.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Frame Buffer Device Development
<linux-fbdev@vuser.vu.union.edu>,
A2232@gmx.net,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] devices.txt bugs
Date: Tue, 2 Jan 2001 18:16:14 +0100 [thread overview]
Message-ID: <20010102181614.G27745@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.05.10101021122180.7140-100000@callisto.of.borg>
In-Reply-To: <Pine.LNX.4.05.10101021122180.7140-100000@callisto.of.borg>; from geert@linux-m68k.org on Tue, Jan 02, 2001 at 11:27:33AM +0100
Hi,
On Tue, Jan 02, Geert Uytterhoeven wrote:
> This patch fixes two things:
>
> - Correct the minor numbers for the frame buffer devices. We have room for
> 32 frame buffers since about one year, with more room for future expansion
> to 256. (promised to go in by HPA on Fri, 24 Mar 2000 01:47:05 -0800).
>
> - Fix a typo in the minors for the A2232 serial card
>
> --- linux-2.4.0-current/Documentation/devices.txt.orig Mon Jan 1 23:30:06 2001
> +++ linux-2.4.0-current/Documentation/devices.txt Tue Jan 2 11:16:42 2001
> @@ -660,6 +660,12 @@
>
> 29 char Universal frame buffer
> 0 = /dev/fb0 First frame buffer
> + 1 = /dev/fb1 Second frame buffer
> + ...
> + 31 = /dev/fb31 32nd frame buffer
> +
> + Backward compatibility aliases {2.6}
> +
> 32 = /dev/fb1 Second frame buffer
How is this supposed to work? /dev/fb1 can either be 29,1 or 29,32. But
not both at the same time.
[...]
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
-o)
Hubert Mantel Goodbye, dots... /\\
_\_v
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-02 17:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-02 10:27 [PATCH] devices.txt bugs Geert Uytterhoeven
2001-01-02 17:16 ` Hubert Mantel [this message]
2001-01-02 20:09 ` H. Peter Anvin
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=20010102181614.G27745@suse.de \
--to=mantel@suse.de \
--cc=A2232@gmx.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=device@lanana.org \
--cc=geert@linux-m68k.org \
--cc=linux-fbdev@vuser.vu.union.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.