From: Mark Meade <mark@lakeshoremicro.com>
To: Ilguiz Latypov <ilatypov@superbt.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [patch] doc_stage1.S : GRUB on DoC
Date: Fri, 2 Aug 2002 09:37:08 -0400 [thread overview]
Message-ID: <200208020933750.SM02488@there> (raw)
In-Reply-To: <Pine.LNX.4.44.0208011941330.25251-100000@server.superbt.com>
Ilguiz Latypov wrote:
> Would this modification make a difference? It seems we read the first
> flash block into a different address when identifying the chip.
This didn't make any difference. It still works find on the faster machine;
reboots on the P133.
Using GRUBSTART:0 is probably the better way to do this: GRUBSTART:0 is
equivalent to GRUBLOADSEG:GRUBLOADOFS (8200:0, 07E0:400), and using zero as
the offset causes the "read block" command to send an address of 0 after
sending the READID command, similar to the way it's done in bdev_diskonchip.c.
Either way, the result (mfg/id code) temporarily ends up at 8200:0, prior to
be replaced by the Grub code.
Mark
> - movw $1, %cx /* read just one page */
> - movw $GRUBSTART, %ax
> + movw $1, %cx /* read just one block */
> + movw $GRUBLOADSEG, %ax
> movw %ax, %es
> - movw $0, %di
> + movw $GRUBLOADOFS, %di
> call read_block
next prev parent reply other threads:[~2002-08-02 13:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-16 18:52 [patch] doc_stage1.S : GRUB on DoC Mark Meade
2002-07-17 18:35 ` Ilguiz Latypov
2002-07-30 4:11 ` Ilguiz Latypov
2002-08-01 18:43 ` Mark Meade
2002-08-01 20:53 ` Ilguiz Latypov
2002-08-01 21:21 ` Mark Meade
2002-08-01 23:44 ` Ilguiz Latypov
2002-08-02 13:37 ` Mark Meade [this message]
2002-08-02 14:02 ` Ilguiz Latypov
2002-08-02 19:18 ` Ilguiz Latypov
2002-08-02 19:49 ` Mark Meade
2002-08-02 21:27 ` Ilguiz Latypov
2002-08-02 21:57 ` Ilguiz Latypov
2002-08-06 16:26 ` Mark Meade
-- strict thread matches above, loose matches on Subject: below --
2002-08-01 14:47 Vadim Khmelnitsky
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=200208020933750.SM02488@there \
--to=mark@lakeshoremicro.com \
--cc=ilatypov@superbt.com \
--cc=linux-mtd@lists.infradead.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.