public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Michael Walle <michael@walle.cc>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] lsxl: add support for lschlv2 and lsxhl
Date: Tue, 27 Mar 2012 22:55:59 +0200	[thread overview]
Message-ID: <201203272255.59259.michael@walle.cc> (raw)
In-Reply-To: <F766E4F80769BD478052FB6533FA745D1A2F6FA326@SC-VEXCH4.marvell.com>

Hi,

Am Dienstag 27 M?rz 2012, 13:05:05 schrieb Prafulla Wadaskar:
> > I removed the hardcoded values from the environment and put it into a
> > special rescue mode, so it won't show up until the user is explicitly
> > choosing that mode. I can understand, that hardcoded values are bad
> > but in
> > this case i cannot think of any other (easy and reliable) way to get
> > access to a misconfigured linkstation.
> > 
> > Do you have any other idea? again, the only interfaces you have are
> > ethernet, one button, two (multiple color leds), one switch with three
> > positions [and an usb port, only available on older linkstations].
> 
> You need special environment variables by default, u-boot development
> policy does not allow this, so you can have clean code mainlined and keep
> this customization patch private to you. This is what I think the solution
> could be :-(

Wolfgang, what do you think about relaxing this policy a bit and allowing this 
class of devices (no service port/serial port available, no storage for the 
MAC address besides the environment) to use hardcoded values (maybe defined in 
a place common to all boards). Again, i don't think my device is the only one 
with this problem.


> > mh? the lschlv2_ramboot is just for testing purposes. So you can try
> > the
> > bootloader without actually overwriting it in the boot flash. The
> > actual
> > images are the lschlv2 and lsxhl targets. I guess i should add a
> > lsxhl_ramboot, too. There was no need for the latter because i have a
> > jtag
> > connector on my lsxhl (but not on the lschlv2).
> 
> AFAIK, for ram boot you need u-boot ELF image, you can use u-boot.bin but
> u-boot.kwb image cannot be used for boot from RAM, kwbimage.cfg helps to
> create u-boot.kwb target which is useless for boot from RAM use case. So
> you need to remove it.

The elf/bin is just for testing and the kwb image will be written into the spi 
flash, i need both (at least i need the kwb image). I could remove the ramboot 
target, but i think its really handy if someone likes to play with a self 
compiled uboot.


-- 
Michael

  reply	other threads:[~2012-03-27 20:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-27 10:51 [U-Boot] [PATCH v2] lsxl: add support for lschlv2 and lsxhl Michael Walle
2012-03-27 11:05 ` Prafulla Wadaskar
2012-03-27 20:55   ` Michael Walle [this message]
2012-03-27 21:13     ` Wolfgang Denk
2012-03-29 11:30       ` Michael Walle
  -- strict thread matches above, loose matches on Subject: below --
2012-03-02 15:02 Michael Walle
2012-03-26 10:15 ` Michael Walle
2012-03-27  7:27   ` Prafulla Wadaskar
2012-03-27 20:38     ` Michael Walle
2012-03-29 12:38     ` Michael Walle
2012-03-29 14:24       ` Prafulla Wadaskar
2012-03-29 14:39         ` Michael Walle
2012-03-30 11:18           ` Prafulla Wadaskar
2012-03-30 13:57             ` Michael Walle
2012-04-02  6:37               ` Prafulla Wadaskar
2012-03-27  7:28   ` Prafulla Wadaskar

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=201203272255.59259.michael@walle.cc \
    --to=michael@walle.cc \
    --cc=u-boot@lists.denx.de \
    /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