public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Miguel Freitas" <miguel@cetuc.puc-rio.br>
To: Ciro Cattuto <ciro@prosa.it>
Cc: mtd@infradead.org, David Woodhouse <dwmw2@infradead.org>
Subject: Re: GRUB on DOC: 2Mb issues
Date: Mon, 28 Aug 2000 19:24:09 GMT-3	[thread overview]
Message-ID: <129C7B9418F@mamao.cetuc.puc-rio.br> (raw)
In-Reply-To: <20000828185018.A2777@localhost>

On 28 Aug 00, at 18:50, Ciro Cattuto wrote:

> Also, doc_stage1.S doesn't support the
> addressing scheme needed for 2Mb DOCs, so I had to make a few
> modifications to make it load GRUB-stage2.

   I haven't tried your modifications yet, but IMHO it looks right. The  
doc_stage1 should work on both 256 and 512 paged devices without 
any conditionals. The loop will send a READ0 command, set 
address such as column(byte)=0 and page(word)=counter++ and 
read 256 bytes. Of course stage2 needs to be written as described 
in mtd/grub/README.
   It may also be a good idea to send an additional address byte 
zero for compatibility with >= 64Mb chips. Datasheet of 2MB says 
this additional byte would be ignored, but I need to check for all 
other chips.

> The relevant cvs diffs follow. Notice: these mods make doc_stage1.S and
> makecsum.c work _only_ for 2Mb DOCs! I'd like to merge this functionality
> into the existing code, but I'll wait for your feedback. I'd use a simple
> "#ifdef DOC_PAGE256" both in doc_stage1.S and makecsum.c, but in the long
> run it would be nice to be able to access the page256 flag
> (mtd->priv->page256) from userland (page256 in mtd_info_user?).

   I don't really like userland tools (eg. makecsum or doc_loadbios) 
taking care of such details as addressing mechanism of nand chips. 
I guess it would be better to create an ioctl called "loadbios" and 
handle that odditys inside the kernel driver. If page256==1, just write 
the 8kb image. If page256==0, write 512 byte pages padding with 
0xff the unused bytes.


Regards,

Miguel Freitas



To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

  reply	other threads:[~2000-08-28 22:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-28 16:50 GRUB on DOC: 2Mb issues Ciro Cattuto
2000-08-28 22:24 ` Miguel Freitas [this message]
2000-08-30  8:57 ` David Woodhouse
2000-08-30 13:46   ` Miguel Freitas
2000-08-30 15:07     ` David Woodhouse
2000-08-30 14:23       ` Miguel Freitas
2000-08-31 16:20         ` David Woodhouse
2000-08-31 23:10           ` Ciro Cattuto
2000-08-30 15:47       ` Ciro Cattuto
2000-08-30 16:31       ` David Woodhouse
2000-08-30 16:39         ` David Woodhouse
2000-08-30 14:21   ` Ciro Cattuto

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=129C7B9418F@mamao.cetuc.puc-rio.br \
    --to=miguel@cetuc.puc-rio.br \
    --cc=ciro@prosa.it \
    --cc=dwmw2@infradead.org \
    --cc=mtd@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