mail archive of the barebox mailing list
 help / color / mirror / Atom feed
* how easy to add extra config for NAND-less beagle?
@ 2012-11-15 14:36 Robert P. J. Day
  2012-11-15 16:16 ` Sascha Hauer
  0 siblings, 1 reply; 6+ messages in thread
From: Robert P. J. Day @ 2012-11-15 14:36 UTC (permalink / raw)
  To: U-Boot Version 2 (barebox)


  returning to playing with barebox after lengthy hiatus and i asked
an equivalent question on the u-boot list, let's see if it's relevant
here.

  i did a regular configure and build for my beagle xM (rev C) which,
unlike the beagle classic, has no NAND flash:

$ make omap3530_beagle_xload_defconfig ; make
$ make omap3530_beagle_defconfig ; make

then copied MLO and barebox.bin to an appropriate card and, lo, it
booted nicely and i'm currently sitting in barebox:

  barebox@Texas Instrument's Beagle:/ version

  barebox 2012.10.0-00283-gd65d9df #2 Thu Nov 15 06:45:21 EST 2012

thing is, this build has a good deal of NAND-related functionality
that is of no use whatsoever on the current beagle xMs, so i'm
interested in how little work it would take to add an extra config
that would deselect everything related to NAND.  (obviously, having
that functionality there doesn't *hurt*, but i'm planning to use
barebox in my new embedded linux courses and it would be nice to be
able to build for an xM and have it *totally* correspond to the actual
hardware.)  it shouldn't be hard -- simply deselecting anything
related to NAND, MTD or JFFS2 should do the trick.

rday

p.s.  when i run "devinfo", i see a couple NAND-related entries:

devices:
... snip ...
`---- gpmc_nand0
... snip ...

drivers:
... snip ...
 gpmc_nand
... snip ...

  somewhat embarrassed to admit that i don't know what "gpmc_nand"
represents, but i'll google shortly.  however, no matter what it is,
would it be relevant on a board with no NAND flash?  thanks muchly for
any advice.



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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: how easy to add extra config for NAND-less beagle?
  2012-11-15 14:36 how easy to add extra config for NAND-less beagle? Robert P. J. Day
@ 2012-11-15 16:16 ` Sascha Hauer
  2012-11-15 16:39   ` Robert P. J. Day
  0 siblings, 1 reply; 6+ messages in thread
From: Sascha Hauer @ 2012-11-15 16:16 UTC (permalink / raw)
  To: Robert P. J. Day; +Cc: U-Boot Version 2 (barebox)

Hi Robert,

On Thu, Nov 15, 2012 at 09:36:37AM -0500, Robert P. J. Day wrote:
> 
>   returning to playing with barebox after lengthy hiatus and i asked
> an equivalent question on the u-boot list, let's see if it's relevant
> here.
> 
>   i did a regular configure and build for my beagle xM (rev C) which,
> unlike the beagle classic, has no NAND flash:
> 
> $ make omap3530_beagle_xload_defconfig ; make
> $ make omap3530_beagle_defconfig ; make
> 
> then copied MLO and barebox.bin to an appropriate card and, lo, it
> booted nicely and i'm currently sitting in barebox:
> 
>   barebox@Texas Instrument's Beagle:/ version
> 
>   barebox 2012.10.0-00283-gd65d9df #2 Thu Nov 15 06:45:21 EST 2012
> 
> thing is, this build has a good deal of NAND-related functionality
> that is of no use whatsoever on the current beagle xMs, so i'm
> interested in how little work it would take to add an extra config
> that would deselect everything related to NAND.  (obviously, having
> that functionality there doesn't *hurt*, but i'm planning to use
> barebox in my new embedded linux courses and it would be nice to be
> able to build for an xM and have it *totally* correspond to the actual
> hardware.)  it shouldn't be hard -- simply deselecting anything
> related to NAND, MTD or JFFS2 should do the trick.

Disable MTD support and if you want also the protect/erase commands:

make menuconfig

Drivers                         --->
  [ ] Memory Technology Device (MTD) support  --->

commands                        --->
  flash                           --->
    [ ] protect/erase

Saves you around 35Kb of binary space

> 
> rday
> 
> p.s.  when i run "devinfo", i see a couple NAND-related entries:
> 
> devices:
> ... snip ...
> `---- gpmc_nand0

The nand device, probably present even when you disable nand support.
However, no driver will bind to it if you disable it.

Sascha


-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: how easy to add extra config for NAND-less beagle?
  2012-11-15 16:16 ` Sascha Hauer
@ 2012-11-15 16:39   ` Robert P. J. Day
  2012-11-15 19:22     ` Jean-Christophe PLAGNIOL-VILLARD
  2012-11-15 19:26     ` Sascha Hauer
  0 siblings, 2 replies; 6+ messages in thread
From: Robert P. J. Day @ 2012-11-15 16:39 UTC (permalink / raw)
  To: Sascha Hauer; +Cc: U-Boot Version 2 (barebox)

On Thu, 15 Nov 2012, Sascha Hauer wrote:

> Hi Robert,
>
> On Thu, Nov 15, 2012 at 09:36:37AM -0500, Robert P. J. Day wrote:
> >
> >   returning to playing with barebox after lengthy hiatus and i asked
> > an equivalent question on the u-boot list, let's see if it's relevant
> > here.
> >
> >   i did a regular configure and build for my beagle xM (rev C) which,
> > unlike the beagle classic, has no NAND flash:
> >
> > $ make omap3530_beagle_xload_defconfig ; make
> > $ make omap3530_beagle_defconfig ; make
> >
> > then copied MLO and barebox.bin to an appropriate card and, lo, it
> > booted nicely and i'm currently sitting in barebox:
> >
> >   barebox@Texas Instrument's Beagle:/ version
> >
> >   barebox 2012.10.0-00283-gd65d9df #2 Thu Nov 15 06:45:21 EST 2012
> >
> > thing is, this build has a good deal of NAND-related functionality
> > that is of no use whatsoever on the current beagle xMs, so i'm
> > interested in how little work it would take to add an extra config
> > that would deselect everything related to NAND.  (obviously, having
> > that functionality there doesn't *hurt*, but i'm planning to use
> > barebox in my new embedded linux courses and it would be nice to be
> > able to build for an xM and have it *totally* correspond to the actual
> > hardware.)  it shouldn't be hard -- simply deselecting anything
> > related to NAND, MTD or JFFS2 should do the trick.
>
> Disable MTD support and if you want also the protect/erase commands:
>
> make menuconfig
>
> Drivers                         --->
>   [ ] Memory Technology Device (MTD) support  --->
>
> commands                        --->
>   flash                           --->
>     [ ] protect/erase
>
> Saves you around 35Kb of binary space

  yup, i'm testing that shortly, but my question was more along the
lines of, rather than having to disable all NAND-related
functionality *manually*, how easy/worthwhile would it be to create an
additional make target that reflects a beagle *without* NAND flash?

  one significant difference between a classic beagle and a current xM
is the total lack of NAND flash, and that's not a minor difference.
it means you can remove all barebox functionality related to that --
NAND routines and support, MTD stuff, JFFS2(?) support, and so on.
this could be automated by creating a couple new configs, say:

  make dm3730_beaglexm_xload_defconfig
  make dm3730_beaglexm_defconfig

so that the result really matches the underlying board.

  is this worth doing?  it would seem to be fairly easy, i can whip
something up and test it.

rday

p.s.  there are other significant differences as well -- onboard
ethernet, 4-port USB hub.  it seems to me that there is enough of a
difference to warrant a separate configuration.  thoughts?

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================


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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: how easy to add extra config for NAND-less beagle?
  2012-11-15 16:39   ` Robert P. J. Day
@ 2012-11-15 19:22     ` Jean-Christophe PLAGNIOL-VILLARD
  2012-11-15 19:26     ` Sascha Hauer
  1 sibling, 0 replies; 6+ messages in thread
From: Jean-Christophe PLAGNIOL-VILLARD @ 2012-11-15 19:22 UTC (permalink / raw)
  To: Robert P. J. Day; +Cc: U-Boot Version 2 (barebox)

On 11:39 Thu 15 Nov     , Robert P. J. Day wrote:
> On Thu, 15 Nov 2012, Sascha Hauer wrote:
> 
> > Hi Robert,
> >
> > On Thu, Nov 15, 2012 at 09:36:37AM -0500, Robert P. J. Day wrote:
> > >
> > >   returning to playing with barebox after lengthy hiatus and i asked
> > > an equivalent question on the u-boot list, let's see if it's relevant
> > > here.
> > >
> > >   i did a regular configure and build for my beagle xM (rev C) which,
> > > unlike the beagle classic, has no NAND flash:
> > >
> > > $ make omap3530_beagle_xload_defconfig ; make
> > > $ make omap3530_beagle_defconfig ; make
> > >
> > > then copied MLO and barebox.bin to an appropriate card and, lo, it
> > > booted nicely and i'm currently sitting in barebox:
> > >
> > >   barebox@Texas Instrument's Beagle:/ version
> > >
> > >   barebox 2012.10.0-00283-gd65d9df #2 Thu Nov 15 06:45:21 EST 2012
> > >
> > > thing is, this build has a good deal of NAND-related functionality
> > > that is of no use whatsoever on the current beagle xMs, so i'm
> > > interested in how little work it would take to add an extra config
> > > that would deselect everything related to NAND.  (obviously, having
> > > that functionality there doesn't *hurt*, but i'm planning to use
> > > barebox in my new embedded linux courses and it would be nice to be
> > > able to build for an xM and have it *totally* correspond to the actual
> > > hardware.)  it shouldn't be hard -- simply deselecting anything
> > > related to NAND, MTD or JFFS2 should do the trick.
> >
> > Disable MTD support and if you want also the protect/erase commands:
> >
> > make menuconfig
> >
> > Drivers                         --->
> >   [ ] Memory Technology Device (MTD) support  --->
> >
> > commands                        --->
> >   flash                           --->
> >     [ ] protect/erase
> >
> > Saves you around 35Kb of binary space
> 
>   yup, i'm testing that shortly, but my question was more along the
> lines of, rather than having to disable all NAND-related
> functionality *manually*, how easy/worthwhile would it be to create an
> additional make target that reflects a beagle *without* NAND flash?
> 
>   one significant difference between a classic beagle and a current xM
> is the total lack of NAND flash, and that's not a minor difference.
> it means you can remove all barebox functionality related to that --
> NAND routines and support, MTD stuff, JFFS2(?) support, and so on.
> this could be automated by creating a couple new configs, say:
> 
>   make dm3730_beaglexm_xload_defconfig
>   make dm3730_beaglexm_defconfig
> 
> so that the result really matches the underlying board.
> 
>   is this worth doing?  it would seem to be fairly easy, i can whip
> something up and test it.
> 
> rday
> 
> p.s.  there are other significant differences as well -- onboard
> ethernet, 4-port USB hub.  it seems to me that there is enough of a
> difference to warrant a separate configuration.  thoughts?
no can you detect it?

on at91 we have teh 9x5ek which can a 5 different soc with different daughter

which we detetct

Best Regards,
J.
> 
> -- 
> 
> ========================================================================
> Robert P. J. Day                                 Ottawa, Ontario, CANADA
>                         http://crashcourse.ca
> 
> Twitter:                                       http://twitter.com/rpjday
> LinkedIn:                               http://ca.linkedin.com/in/rpjday
> ========================================================================
> 
> 
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: how easy to add extra config for NAND-less beagle?
  2012-11-15 16:39   ` Robert P. J. Day
  2012-11-15 19:22     ` Jean-Christophe PLAGNIOL-VILLARD
@ 2012-11-15 19:26     ` Sascha Hauer
  2012-11-16 11:16       ` Robert P. J. Day
  1 sibling, 1 reply; 6+ messages in thread
From: Sascha Hauer @ 2012-11-15 19:26 UTC (permalink / raw)
  To: Robert P. J. Day; +Cc: U-Boot Version 2 (barebox)

On Thu, Nov 15, 2012 at 11:39:58AM -0500, Robert P. J. Day wrote:
> 
>   yup, i'm testing that shortly, but my question was more along the
> lines of, rather than having to disable all NAND-related
> functionality *manually*, how easy/worthwhile would it be to create an
> additional make target that reflects a beagle *without* NAND flash?
> 
>   one significant difference between a classic beagle and a current xM
> is the total lack of NAND flash, and that's not a minor difference.
> it means you can remove all barebox functionality related to that --
> NAND routines and support, MTD stuff, JFFS2(?) support, and so on.
> this could be automated by creating a couple new configs, say:
> 
>   make dm3730_beaglexm_xload_defconfig
>   make dm3730_beaglexm_defconfig
> 
> so that the result really matches the underlying board.
> 
>   is this worth doing?  it would seem to be fairly easy, i can whip
> something up and test it.

I don't think this is worth it. We should rather keep the number of
defconfigs low. Splitting them means we have to maintain them and
keep them in sync. Also it means to increase the time needed to compile
all defconfigs (which I do routinely, currently on every commit).

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: how easy to add extra config for NAND-less beagle?
  2012-11-15 19:26     ` Sascha Hauer
@ 2012-11-16 11:16       ` Robert P. J. Day
  0 siblings, 0 replies; 6+ messages in thread
From: Robert P. J. Day @ 2012-11-16 11:16 UTC (permalink / raw)
  To: Sascha Hauer; +Cc: U-Boot Version 2 (barebox)

On Thu, 15 Nov 2012, Sascha Hauer wrote:

> On Thu, Nov 15, 2012 at 11:39:58AM -0500, Robert P. J. Day wrote:
> >
> >   yup, i'm testing that shortly, but my question was more along the
> > lines of, rather than having to disable all NAND-related
> > functionality *manually*, how easy/worthwhile would it be to create an
> > additional make target that reflects a beagle *without* NAND flash?
> >
> >   one significant difference between a classic beagle and a current xM
> > is the total lack of NAND flash, and that's not a minor difference.
> > it means you can remove all barebox functionality related to that --
> > NAND routines and support, MTD stuff, JFFS2(?) support, and so on.
> > this could be automated by creating a couple new configs, say:
> >
> >   make dm3730_beaglexm_xload_defconfig
> >   make dm3730_beaglexm_defconfig
> >
> > so that the result really matches the underlying board.
> >
> >   is this worth doing?  it would seem to be fairly easy, i can whip
> > something up and test it.
>
> I don't think this is worth it. We should rather keep the number of
> defconfigs low. Splitting them means we have to maintain them and
> keep them in sync. Also it means to increase the time needed to
> compile all defconfigs (which I do routinely, currently on every
> commit).

  ok, that makes sense.  i'll still have a couple questions later on
the proper configuration of barebox for flash-less systems like the
xM.  thanks.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2012-11-16 11:16 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-11-15 14:36 how easy to add extra config for NAND-less beagle? Robert P. J. Day
2012-11-15 16:16 ` Sascha Hauer
2012-11-15 16:39   ` Robert P. J. Day
2012-11-15 19:22     ` Jean-Christophe PLAGNIOL-VILLARD
2012-11-15 19:26     ` Sascha Hauer
2012-11-16 11:16       ` Robert P. J. Day

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox