From: "Bryan W. Headley" <bwheadley@earthlink.net>
To: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] XFree-4.2 and C110
Date: Sun, 30 Jun 2002 09:48:18 -0500 [thread overview]
Message-ID: <3D1F1A32.7060407@earthlink.net> (raw)
Tried the new 4.2.0 snapshots on my C110. It tells me it cannot find the
framebuffer, and can't support 24-bit color (even though 4.1 can).
The system appears to be looking in /proc/bus/pci to look for video
cards and framebuffers, which is a bogus way to find video cards on a
PC, too (VESA bus, ISA, EISA, MCA... where is that video card?)
On the sparc/32, they're going down /proc/openprom to find the video
adapter; I'm wondering if it's appropriate to try to expose the device
list the kernel sees during bootup as a /proc file, and then write a
special handler like they have for "sbus".
I'm not too fond of synthesizing a "pci" directory, and making up fake
IDs for things that aren't PCI cards...
a) anyone already come up with a better solution?
b) if one has to be developed, is a little file in /proc the way to go?
--
____ .:. ____
Bryan W. Headley - bwheadley@earthlink.net
next reply other threads:[~2002-06-30 14:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-30 14:48 Bryan W. Headley [this message]
2002-06-30 22:10 ` [parisc-linux] XFree-4.2 and C110 Matthew Wilcox
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=3D1F1A32.7060407@earthlink.net \
--to=bwheadley@earthlink.net \
--cc=parisc-linux@lists.parisc-linux.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