public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
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 15:49:39 -0400	[thread overview]
Message-ID: <200208021549578.SM02488@there> (raw)
In-Reply-To: <Pine.LNX.4.44.0208020949420.26999-100000@server.superbt.com>

Ilguiz,

Indeed, the READID command doesn't seem to care what address is sent -- the 
answer came back correctly either way.

Here's what I've learned so far:

1)  The Grub CVS code (from 7/30), with the 2002-06-21 patch applied also 
causes the P133 machine to reboot.  This code has none of the combined 
doc_stage1/1b additions made in the 07-29 patch.

2)  The 0.92 Grub, with an earlier doc patch (I think it was 05-30) boots 
fine.

3)  Using the combined doc_stage1/1b with 0.92 Grub does not work.

Again, all three combinations above work just fine on the faster PC.

Item #1 seems to suggest that cvs grub may have introduced the problem, but 
in that case #3 should work.  Item #3 was patched manually (just doc_stage1.S 
and the Makefile), so it's possible I missed something else in your 07-29 
patch.

Anyway, is it possible to take an unmodified 0.92 Grub, and cleanly apply the 
latest (07-29) patch?  I was not able to do this, mainly because of automake 
version differences.  

Thanks,

Mark

Ilguiz Latypov wrote:
> I understand that the same register %di serves as the offset to the
> destination in RAM and as the offset in flash.  And stage2 or doc2000.c
> code will read chip ID from offset 0.  I think the offset may not be
> important because the READID command tells the chip to report the ID.

  parent reply	other threads:[~2002-08-02 19:53 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
2002-08-02 14:02             ` Ilguiz Latypov
2002-08-02 19:18               ` Ilguiz Latypov
2002-08-02 19:49               ` Mark Meade [this message]
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=200208021549578.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox