linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Prakash kanthi <pkanthi@yahoo.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Board specific info for no EEPROM case
Date: Tue, 10 Dec 2002 15:18:53 -0800 (PST)	[thread overview]
Message-ID: <20021210231853.23902.qmail@web41203.mail.yahoo.com> (raw)
In-Reply-To: <20021206024109.S1931@mind.be>


Hi Folks,

I do not have a NVRAM or EEPROM on my board (PPC405
based). I see that during the linux booting, it is
trying to read bd_t info from EEPROM and failing. Is
there an alternative to this problem? Can i hardcode
the stuff in decompress_kernel method and go ahead?

thanks,
Prakash


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2002-12-10 23:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-05 11:18 Target CPU selection for Real time Embedded Linux Alexander.J
2002-12-06  1:41 ` Peter Vandenabeele
2002-12-06 20:55   ` Peter Ryser
2002-12-10 23:18   ` Prakash kanthi [this message]
2002-12-11  0:10     ` Board specific info for no EEPROM case Matt Porter

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=20021210231853.23902.qmail@web41203.mail.yahoo.com \
    --to=pkanthi@yahoo.com \
    --cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).