BOUNCE [e-mail]: Admin request of type /^\s*which\s*$/i at line 9

> From [e-mail]  Wed Feb  9 10:30:01 2000

Received: from avalon.informatik.uni-freiburg.de (avalon.informatik.uni-freiburg.de [132.230.150.1])
    by wesley.informatik.uni-freiburg.de (8.8.8/8.8.8) with ESMTP id KAA01906
    for ; Wed, 9 Feb 2000 10:30:01 +0100
Received: from mailgateway1.uni-freiburg.de (mailgateway1.uni-freiburg.de [132.230.1.6])
    by avalon.informatik.uni-freiburg.de (8.9.0/8.9.0) with SMTP id KAA20273
    for ; Wed, 9 Feb 2000 10:29:58 +0100 (MET)
Received: from cyclone.stortek.com [129.80.22.130] 
    by mailgateway1.uni-freiburg.de with esmtp (Exim 1.82 #3)
    id 12ITRc-0007N1-00; Wed, 9 Feb 2000 10:29:56 +0100
Received: from cyclone.stortek.com (localhost [127.0.0.1])
    by cyclone.stortek.com (8.9.3/8.9.3) with ESMTP id CAA20643
    for ; Wed, 9 Feb 2000 02:24:56 -0700 (MST)
Received: from vinson-atm6.stortek.com ([e-mail] [129.80.120.134])
    by cyclone.stortek.com (8.9.3/8.9.3) with ESMTP id CAA20639
    for ; Wed, 9 Feb 2000 02:24:55 -0700 (MST)
Received: from eur-bridge.europe.stortek.com (eur-bridge.stortek.com [129.80.178.149])
    by vinson-atm6.stortek.com (8.9.3/8.9.3) with ESMTP id CAA12205
    for ; Wed, 9 Feb 2000 02:25:08 -0700 (MST)
Received: by eur-bridge.europe.stortek.com with Internet Mail Service (5.5.2650.21)
    id <1SB7DV5G>; Wed, 9 Feb 2000 09:24:24 -0000
Message-ID: 
From: "Jessen, Per" 
To: "'openbios'" 
Subject: flashing AMD EPROMs under Linux (possibly off-topic)
Date: Wed, 9 Feb 2000 09:23:50 -0000 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
    charset="iso-8859-1"

All,

this is probably off-topic on this list, so my apologies in advance.
But considering the recent debate on the flashing of BIOS'es, I figured
this might be the right place to ask -

I'm trying to flashwrite to an AMD29F010A - 128K flash EPROM. It's sitting
at 0xC000 as a video-ROM. I've got a module (kernel 2.2.14) doing this,
which 
initially caused some problems, but it's more or less working now. 
It's the "more or less" bit that's causing problems :-)

If I leave the 2 first bytes of the ROM-image as 0xFFFF (instead of 0xAA55)
I can flash the EPROM with no problems. If I leave them in, the system
appears to get stuck/hung. No way out, except reset.
If I use 0xFFFF at first, then subsequently try to write 0xAA55, the
system again appears to locks up. 
Prior to a new write, I erase the entire EPROM (not necessary, I know, but
...)
So, what I don't understand is what is the importance of the 0xAA55 to Linux
?
I can flash the EPROM using a DOS utility with absolutely no problems.

If this is the wrong place to ask, could someone point me in the right
direction ?

MTIA
regards,
Per Jessen