All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@yahoo.com>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Exposing ROM's though sysfs
Date: Fri, 30 Jul 2004 09:53:39 -0700 (PDT)	[thread overview]
Message-ID: <20040730165339.76945.qmail@web14929.mail.yahoo.com> (raw)

We talked at OLS about exposing adapter ROMs via sysfs. I have some
time to work on this but I'm not sure about the right places to hook
into the kernel.

The first problem is recording the boot video device. This is needed
for laptops that compress their video and system ROMs together into a
single ROM. When sysfs exposes the ROM for these adapters it needs to
know the boot video device so that it can return the ROM image at
C000:0 instead of trying to find an actual ROM. What is the right
kernel structure for recording the boot video device? Where should this
code live? It is probably x86 specific but have non-x86 laptops done
the same trick?

What about ISA support. Should we make an attempt to return ROM
contents from ISA cards?

Note that not just video cards can have ROMs. Disk adapters commonly
have them too. We probably want to expose these ROMs too.

Do we want to expose the system ROM via sysfs? Where should it appear?

Some Radeon cards have a bug where they forgot to clear a latch which
makes the ROMs visible. Where should a fix for things like this go? I
can put it in the radeon driver but if you try to read the ROM before
the driver is loaded, the ROM won't be visible.

=====
Jon Smirl
jonsmirl@yahoo.com


		
__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail 

             reply	other threads:[~2004-07-30 16:54 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-30 16:53 Jon Smirl [this message]
2004-07-30 17:10 ` Exposing ROM's though sysfs Jesse Barnes
2004-07-30 17:19   ` Jesse Barnes
2004-07-30 17:24   ` Christoph Hellwig
2004-07-30 17:57     ` Jesse Barnes
2004-07-30 18:06       ` Jesse Barnes
2004-07-30 18:12       ` Matthew Wilcox
2004-07-30 18:12         ` Jesse Barnes
2004-07-30 18:20           ` Martin Mares
2004-07-30 18:49           ` Jesse Barnes
2004-07-30 19:55             ` Greg KH
2004-07-30 20:05               ` Jon Smirl
2004-07-30 20:16               ` Jesse Barnes
2004-07-30 20:29                 ` Greg KH
2004-07-30 18:59         ` Jon Smirl
2004-07-30 19:04           ` Matthew Wilcox
2004-07-30 19:30             ` Jon Smirl
2004-07-30 19:35               ` Martin Mares
2004-07-30 19:39                 ` Jon Smirl
2004-07-30 19:46                   ` Martin Mares
2004-07-30 20:03                     ` Jon Smirl
2004-07-30 20:10                       ` Martin Mares
2004-07-30 20:13                         ` Martin Mares
2004-07-30 20:25                           ` Jesse Barnes
2004-07-30 20:32                         ` Jon Smirl
2004-07-30 20:41                           ` Martin Mares
2004-07-30 20:49                             ` Jesse Barnes
2004-07-30 20:54                               ` Martin Mares
2004-07-30 21:00                                 ` Jesse Barnes
2004-07-30 21:07                               ` Jon Smirl
2004-07-30 21:12                                 ` Jesse Barnes
2004-07-30 19:47               ` Vojtech Pavlik
2004-07-30 22:18             ` Thomas Bogendoerfer
2004-07-30 22:39         ` Alan Cox
2004-07-30 19:25   ` Jon Smirl
2004-07-30 19:35     ` Vojtech Pavlik
2004-07-30 19:41       ` Jon Smirl
2004-07-30 19:48         ` Vojtech Pavlik
2004-07-30 20:20           ` Jesse Barnes
2004-07-30 22:41             ` Alan Cox
     [not found] <1091207136.2762.181.camel@rohan.arnor.net>
2004-07-30 17:24 ` Jon Smirl
2004-07-30 19:14   ` Vojtech Pavlik
2004-07-30 20:26     ` Jesse Barnes
2004-07-30 22:36       ` Alan Cox
2004-08-03 21:41         ` Benjamin Herrenschmidt
2004-08-04  0:55           ` Jesse Barnes
2004-08-04  0:59             ` Benjamin Herrenschmidt
2004-08-04  1:37               ` Jon Smirl
2004-08-04  1:57                 ` Benjamin Herrenschmidt
2004-08-04  2:16                   ` Jesse Barnes

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=20040730165339.76945.qmail@web14929.mail.yahoo.com \
    --to=jonsmirl@yahoo.com \
    --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 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.