From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Dave Jones <davej@suse.de>
Cc: linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, diego@biurrun.de, jerry.c.t@web.de,
mike@pieper-family.de, hollis@austin.ibm.com
Subject: Re: Updates to matroxfb: do you want DFP or TVOut on G450/G
Date: Sat, 8 Jun 2002 03:04:51 +0200 [thread overview]
Message-ID: <77417CB2C9F@vcnet.vc.cvut.cz> (raw)
On 8 Jun 02 at 2:57, Dave Jones wrote:
> On Sat, Jun 08, 2002 at 02:45:39AM +0200, Petr Vandrovec wrote:
> > (4) You can read PINS through /proc.
> > (H) Change /proc code to use driverfs instead. Linus refused
> > /proc based code already.
>
> One of the first things I ever wrote for Linux was a PINS decoder.
> It read from /dev/mem to get the PINS structure. Any reason
> why this isn't good enough, and we need the kernel exporting PINS ?
It does not print decoded structure, it shows it in raw format, 64-128
bytes, just to avoid userspace parsing /dev/mem because of matroxfb
did it already (and matroxfb needs PINS to properly initialize Gx50
cards in non-PC hardware). And it may be non-trivial to get PINS from
userspace at all because of BIOSes may be disabled by firmware
(and f.e. on my PC they are disabled for secondary adapters, so
simple parsing /dev/mem leads to nowhere because of BIOS is hidden).
Besides that, it lives in complete separate file, so it is easy
to add/remove it.
Best regards,
Petr Vandrovec
vandrove@vc.cvut.cz
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink
reply other threads:[~2002-06-08 1:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=77417CB2C9F@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=davej@suse.de \
--cc=diego@biurrun.de \
--cc=hollis@austin.ibm.com \
--cc=jerry.c.t@web.de \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mike@pieper-family.de \
/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;
as well as URLs for NNTP newsgroup(s).