public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Rene Herman <rene.herman@keyaccess.nl>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.6.5-mm3, x86_64: probe_roms()
Date: Fri, 9 Apr 2004 19:02:05 +0200	[thread overview]
Message-ID: <20040409190205.1781d33d.ak@suse.de> (raw)
In-Reply-To: <4076CDA5.4090609@keyaccess.nl>

On Fri, 09 Apr 2004 18:21:57 +0200
Rene Herman <rene.herman@keyaccess.nl> wrote:

> Hi Andrew, Andi.
> 
> Andi, this patch sent to Andrew since he has the i386 equivalent. If you 
> want it yourself, or don't want it at all, please holler.
> 
> x86_64 inherits arch/x86_64/kernel/setup.c:probe_roms() from i386 and 
> shares its problems (minus the first) described at:
> 
> http://marc.theaimsgroup.com/?l=linux-kernel&m=107991009932451&w=2
> 
> Like the i386 version, the attached x86_64 version also c99ifies the 
> data and adds IORESOURCE_* type flags. It's been (cross-)compiled but 
> not booted due to lack of hardware.

The C99ification is really ugly, because the tables end up more or less 
unreadable unlike the previous version.  I don't think it's a good 
idea to use values from the ROM unchecked (like you did with the length
for the checksum). In fact this checksum change looks quite dangerous on i386
because there is very likely a machine out somewhere with bogus
length bytes which explodes when you do an access after the video ROM.
Chipsets sometimes have interesting errata in these areas.
[that's probably more an issue on i386 than on x86-64, but it's better
to be safe than sorry]

The other changes look ok. If you send me a patch just for these 
I will apply it.

-Andi

  reply	other threads:[~2004-04-09 17:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-09 16:21 [PATCH] 2.6.5-mm3, x86_64: probe_roms() Rene Herman
2004-04-09 17:02 ` Andi Kleen [this message]
2004-04-09 22:21   ` Rene Herman

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=20040409190205.1781d33d.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rene.herman@keyaccess.nl \
    /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