mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org, Bahadir Balban <bbalban@b-labs.com>
Subject: Re: [PATCH] Add basic support from ARM Versatile/PB
Date: Mon, 11 Oct 2010 17:23:04 +0200	[thread overview]
Message-ID: <20101011152304.GD7412@game.jcrosoft.org> (raw)
In-Reply-To: <20101011144836.GB28242@pengutronix.de>

On 16:48 Mon 11 Oct     , Sascha Hauer wrote:
> On Mon, Oct 11, 2010 at 04:41:29PM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > On 23:15 Sun 10 Oct     , Alexey Zaytsev wrote:
> > > Signed-off-by: Alexey Zaytsev <alexey.zaytsev@gmail.com>
> > > ---
> > > 
> > > Hi.
> > > 
> > > It seems that barebox does not run on any ARM machines provided
> > > by QEMU. This patch adds basic Versatile/PB support. It is far from
> > > being complete and has not been tested on real hardware, but
> > > seems to work fine in QEMU.
> > > 
> > > Please notice, that you need to set CONFIG_VERSATILE_SMC91C111
> > > in order to have networking in QEMU, as it does not provide
> > > smc91x found on the real hardware.
> > > 
> > > For a queck test, run:
> > > 
> > > 	qemu-system-arm -kernel barebox.bin -M versatilepb -cpu arm926 -nographic -m 64 -net nic,model=smc91c111 -net user
> > this must be in a doc
> > 
> > please use defaultenv and enable more functionnability
> > 
> > as we can use it as ref board for emulation
> > > 
> > > 
> > > +
> > > +config BOARDINFO
> > > +	default "ARM Versatile/PB (ARM926EJ-S)"
> > > +endif
> > > +
> > > +config VERSATILE_SMC91C111
> > > +	bool "Use smc91c111 instead of smc91x (for QEMU)"
> > > +	default 0
> > ??
> > > +	help
> > > +	 Enable this option to run barebox inside qemu.
> > > +	 Real versatile boards are equipped with smc911x,
> > > +	 but qemu only provides smc91111, which is a bit different.
> > it will be beter to modify the ressources depending on the drivers enabled
> 
> I think it's ok the way Alexey did this. It's a good place to document
> that we need two different ethernet drivers depending on native/qemu
> compilation.
yeah but just enable the drivers is enough but we need to make it exclusive
via Kconfig otherwise it will be confusing

Best Regards,
J.

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2010-10-11 15:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-10 23:15 Alexey Zaytsev
2010-10-11  4:56 ` Baruch Siach
2010-10-11  7:22   ` Alexey Zaytsev
2010-10-11 14:41 ` Jean-Christophe PLAGNIOL-VILLARD
2010-10-11 14:48   ` Sascha Hauer
2010-10-11 15:23     ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2010-10-11 14:49   ` Alexey Zaytsev
2010-12-11  7:18 Jean-Christophe PLAGNIOL-VILLARD

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=20101011152304.GD7412@game.jcrosoft.org \
    --to=plagnioj@jcrosoft.com \
    --cc=barebox@lists.infradead.org \
    --cc=bbalban@b-labs.com \
    --cc=s.hauer@pengutronix.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