date:20100518

Re: [U-Boot] U-Boot public API example desired

2010-05-18 Thread James E. Chargin Jr.

This is a reposted and slightly reformatted version of a previous post,
please see http://lists.denx.de/pipermail/u-boot/2010-May/071243.html. I
did not receive a response to my previous post, so I am trying again.

Dear jimc at sdateam.com,

In message 8139.1273161587 at sdateam.com you wrote:

Is there an example available of the use of the U-Boot public API
or of a stand-alone application, that can be, or is, sanctioned by
someone who would definitely know (for example, Wolfgang Denk) as
being not a derived work?

The code in the examples/standalone/ is supposed to provide example
code, and doc/README.standalone is supposed to provide documentation.

I appreciate the answer, I think this topic has been discussed several
times, so thanks for spending time re-visiting it once again.

I have looked at both the examples/standalone code and the
README.standalone.

I've seen several discussions in various mailing lists about these
interfaces but I have not seen a definite example that qualifies. It

What are these various mailing lists, and what exactluy is not clear
to you?

I have also seen
1)
http://old.nabble.com/-U-Boot--How-to-get-GPL-free-standalone-programs-with-u-boot-td27182861.html
2) http://lists.denx.de/pipermail/u-boot/2009-August/058650.html
3) http://osdir.com/ml/boot-loaders.u-boot/2003-11/msg00072.html
4) http://osdir.com/ml/freebsd.embedded/2008-01/msg00019.html
5)
http://old.nabble.com/Re%3A--U-Boot--How-to-get-GPL-free-standalone-programs-with-u-boot-p27338654.html

Some of these are forums, rather that mailing lists, I apologize for
not being specific in my previous message.

Best regards,

Wolfgang Denk

The part that is not clear to me is if a conclusion has ever been
reached as to the availability of a set of GPL-free headers that can be
included in a stand-alone application. I think the GPL is quite
valuable, but there are situations involving closed-source software
where GPL licensed source files must be avoided (I'm sure this is news
to nobody). Has such a set of GPL-free headers been developed, or must I
develop them myself if I want to use them?

In 5) above, you write
In message you wrote:

I have a question concerning standalone programs based on u-boot and
GPL, since I'm not really sure whether the way how the u-boot source
files are set up allows GPL free standalone programs.

This is the intention; if the current code or documentation should
conflict with this intention, it should be fixed.

and

exports.h should be added to the allowed file list; there should
be no need to include common.h. Eventually this needs fixing.
Patches are welcome.

In the latest U-Boot sources, this issue seems to still exist; headers
available for inclusion in stand-alone application seem to include the
GPL license language. I can't find equivalent headers that are
GPL-free, but maybe I am looking in the wrong place.

This last comment includes mention of the allowed file list; I can't
locate anything of this nature either.

Again, thank you for your time and best regards,
Jim
--
James E. Chargin Jr.
Sierra Design Associates(530) 478-6689
117 New Mohawk Rd, Suite H jimc at sdateam.com [13]
Nevada City, CA 95959 USA http:\www.sdateam.com [14]

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] Support for MB86R01 cpu

2010-05-18 Thread Thirumalai

Hi Matthias,
I am going to use u-boot alone for my development. Which debugger is 
suitable for debugging u-boot and initial board bringup activity?
My choice is BDI2000. Is it ok.
Also tell me what toolchains need to be used. Is ELDK supports?
Whether the video driver is available on u-boot ?
-Thirumalai

- Original Message - 
From: Matthias Weißer weiss...@arcor.de
To: Thirumalai thirumala...@datapatterns.co.in
Cc: u-boot@lists.denx.de
Sent: Tuesday, May 18, 2010 11:18 AM
Subject: Re: [U-Boot] Support for MB86R01 cpu


 Hello Thirumalai

 Am 18.05.2010 07:37, schrieb Thirumalai:
 Hi Matthias,
  We are using MB86R01 processor in our design. We just want to 
 know
 what emulator/debugger can be used for initial board bring-up activity 
 and
 also whether the latest u-boot(2010.03) is supporting this processor ?

 I recently posted a patch series adding support for MB86R01 to u-boot. I 
 did not receive any comments on V2 so I thinks its more or less fine and I 
 hope it will be merged within the upcoming merge window.

 See http://lists.denx.de/pipermail/u-boot/2010-May/071097.html for the 
 initial mail of the patch series.

 I am using a BDI2000 (http://www.abatron.ch/products/bdi-family.html) for 
 initial flash programming. A Segger JLink 
 (http://www.segger.com/cms/jlink.html) works also.

 Hope this helped.

 Matthias 

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

[U-Boot] CONFIG_SYS_LINUX_LOWMEM_MAX_SIZE

2010-05-18 Thread anup behare

Hi,

We are using taishan based board having 1GB DDR.
In u-boot code we found that CONFIG_SYS_LINUX_LOWMEM_MAX_SIZE is set to
768MB hence if (size  bootm_size) condition becomes true and u-boot throw
WARNING: adjusting available memory to 0x3000 message on console.

Let me know will it possible to set CONFIG_SYS_LINUX_LOWMEM_MAX_SIZE to 1GB
or is there any fix for above warning message?

Regards,
Anup
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

[U-Boot] *** Warning - bad CRC, using default environment

2010-05-18 Thread anup behare

Hi,

While using u-boot for ppc440 based board we are getting *** Warning - bad
CRC, using default environment message.
On denx site we came to know that message is printed because the flash
sector or ERPROM containing the environment variables has never been
initialized yet.
Is there any fix to remove this warning  message without passing the saveenv
command on u-boot prompt?

~Anup
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] [PATCH v2] Add support for LPC2468 from NXP

2010-05-18 Thread Remco Poelstra

On 12-05-10 18:09, Wolfgang Denk wrote:
 I just see that my mail client wrapped the lines again on send. I'll see
 how I can fix this. I don't think it's a problem right now, I doubt the
 patch will be completely fine this time.
  
 Yes, it is a problem, because I cannot apply it for testing, nur run
 any automatic checking tools over it.



Hi,

Yesterday I tried resending my patch using 'git send-email'. I received
an aknowledgement from Mailman, but the message didn't show up on the list.
Did I do something wrong? Can someone check the Mailman logs?

Kind regards,

Remco Poelstra
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] [PATCH v2] Add support for LPC2468 from NXP

2010-05-18 Thread Anatolij Gustschin

On Tue, 18 May 2010 09:39:54 +0200
Remco Poelstra remco.poels...@duran-audio.com wrote:

 On 12-05-10 18:09, Wolfgang Denk wrote:
  I just see that my mail client wrapped the lines again on send. I'll see
  how I can fix this. I don't think it's a problem right now, I doubt the
  patch will be completely fine this time.
   
  Yes, it is a problem, because I cannot apply it for testing, nur run
  any automatic checking tools over it.
 
 
 
 Hi,
 
 Yesterday I tried resending my patch using 'git send-email'. I received
 an aknowledgement from Mailman, but the message didn't show up on the list.
 Did I do something wrong? Can someone check the Mailman logs?

No. You have send your patch two times and both patches showed up
on the list. See
http://lists.denx.de/pipermail/u-boot/2010-May/071528.html
or
http://lists.denx.de/pipermail/u-boot/2010-May/071541.html

Best regards,
Anatolij
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] *** Warning - bad CRC, using default environment

2010-05-18 Thread Stefan Roese

On Tuesday 18 May 2010 09:11:16 anup behare wrote:
 While using u-boot for ppc440 based board we are getting *** Warning - bad
 CRC, using default environment message.
 On denx site we came to know that message is printed because the flash
 sector or ERPROM containing the environment variables has never been
 initialized yet.
 Is there any fix to remove this warning  message without passing the
 saveenv command on u-boot prompt?

No, these is no fix, since this is not a bug but a desired feature.

Why do you want to change this behaviour? Don't you have any environment 
storage area at all? Then you should define CONFIG_ENV_IS_NOWHERE in your 
board config header.

Cheers,
Stefan

--
DENX Software Engineering GmbH,  MD: Wolfgang Denk  Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: off...@denx.de
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] CONFIG_SYS_LINUX_LOWMEM_MAX_SIZE

2010-05-18 Thread Stefan Roese

Hi Anup,

On Tuesday 18 May 2010 09:03:25 anup behare wrote:
 We are using taishan based board having 1GB DDR.
 In u-boot code we found that CONFIG_SYS_LINUX_LOWMEM_MAX_SIZE is set to
 768MB hence if (size  bootm_size) condition becomes true and u-boot
 throw WARNING: adjusting available memory to 0x3000 message on
 console.
 
 Let me know will it possible to set CONFIG_SYS_LINUX_LOWMEM_MAX_SIZE to 1GB
 or is there any fix for above warning message?

Linux lowmem size is 768MB for PowerPC. Loading at a higher address results 
in a non-booting Linux kernel. So this warning makes sense and it's not 
possible to load to 1GB.

Why do you want to change this? Does this cause you any troubles? Is Linux not 
booting correctly? I don't see what you would gain by loading to 1GB.

Cheers,
Stefan

--
DENX Software Engineering GmbH,  MD: Wolfgang Denk  Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: off...@denx.de
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] hardware flash protect kept during a reboot?

2010-05-18 Thread Stefan Roese

On Monday 17 May 2010 16:11:22 Timur Tabi wrote:
 Stefan Roese wrote:
  This protection is chip specific. IIRC, then some Intel (Strata) chips
  either protect all sectors or have a sectore-wise protection mechanism.
  You need to check your FLASH documentation for the exact behaviour.
  Which chip are you using?
 
 I just want to know whether hardware protection works at all for anyone
 through a reboot.  Is the CFI protect sector command persistent through a
 hardware power reset or power loss?

Yes. Its working at least for Intel Strata FLASH chips.

Cheers,
Stefan

--
DENX Software Engineering GmbH,  MD: Wolfgang Denk  Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: off...@denx.de
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] [PATCH 0/1] Fix hang trying to protect flash sectors

2010-05-18 Thread Stefan Roese

Hi Mark,

On Tuesday 18 May 2010 07:26:34 Mark Tomlinson wrote:
 Our hardware has part of the flash mapped in two address ranges.
 The CONFIG_SYS_MONITOR_BASE is in the upper 'boot' area, whereas
 the CONFIG_SYS_FLASH_BANKS_LIST has the full flash available at
 a lower address.

Just to be sure: You have 2 FLASH chips? Mapped at which addresses? And where 
does CONFIG_SYS_MONITOR_BASE point to?
 
 This all works fine until the code in cfi_flash.c:flash_init(), which
 uses flash_get_info() to find the flash_info_t associated with the
 monitor and environment. These are not in the probed flash range, so
 flash_get_info() returns NULL.

You mean that flash_get_info(CONFIG_SYS_MONITOR_BASE) returns NULL? Please 
explain again, why is this the case? 

 This is not checked and is passed
 directly to flash_protect(). Since flash_protect() was not checking
 for this NULL pointer either, random memory would be clobbered
 causing the device to lock up.
 
 This patch changes flash_protect() to check for the NULL, and the
 error goes unreported.

I would prefer to fix the real problem, that flash_get_info() returns NULL, 
instead.
 
Cheers,
Stefan

--
DENX Software Engineering GmbH,  MD: Wolfgang Denk  Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: off...@denx.de
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

[U-Boot] [PATCH] Fixed two typos in arch/powerpc/cpu/mpc83xx/start.S.

2010-05-18 Thread Horst Kronstorfer


Signed-off-by: Horst Kronstorfer hkron...@frequentis.com
---
 arch/powerpc/cpu/mpc83xx/start.S |4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/powerpc/cpu/mpc83xx/start.S b/arch/powerpc/cpu/mpc83xx/start.S
index a7c8079..aa263e3 100644
--- a/arch/powerpc/cpu/mpc83xx/start.S
+++ b/arch/powerpc/cpu/mpc83xx/start.S
@@ -507,7 +507,7 @@ init_e300_core: /* time t 10 */
 
lis r3, config_sys_i...@h
 #if defined(CONFIG_WATCHDOG)
-   /* Initialise the Wathcdog values and reset it (if req) */
+   /* Initialise the Watchdog values and reset it (if req) */
/*--*/
lis r4, CONFIG_SYS_WATCHDOG_VALUE
ori r4, r4, (SWCRR_SWEN | SWCRR_SWRI | SWCRR_SWPR)
@@ -520,7 +520,7 @@ init_e300_core: /* time t 10 */
li  r4, -0x55C7
sth r4, sw...@l(r3)
 #else
-   /* Disable Wathcdog  */
+   /* Disable Watchdog  */
/*---*/
lwz r4, SWCRR(r3)
/* Check to see if its enabled for disabling
-- 
1.7.1

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] [PATCH 0/3] Makefile: rework / cleanup

2010-05-18 Thread Detlev Zundel

Hi Wolfgang,

 The top level Makefile is growing and growing. Once, wehn we suppoted
 only a few tens of boards, it was possible to implement board
 configuration logic in the Makefile, but it quickly turned out that
 this doesn't scale. Also, it is not really needed (at least not any
 more) - we noch have mechanisnms in place, that allow for more
 efficient code.

 The following patch series is an attempt to start some cleanup and
 reduce the size of the top level Makefile.  The solution is neither
 perfect nor complete - there are quite a lot of boards that resist
 such a cleanup and need more thorough cleanup.  But it's an initial
 step, showing what could and should be done, which boards have
 problems, and why this is the case.  Eentually this paves the ground
 for a more friendly way to add new board configurations.

Wow, thanks for these cleanups.  This is absolutely a good direction to
simplify the makefile.  For all three parts you have my

Acked-by: Detlev Zundel d...@denx.de

Cheers
  Detlev

-- 
As a general remark, you're more likely to get meaningful feedback if you just
submit what you think is best. You'll get more feedback when people don't like
what you did,  but any  EE will tell you that negative feedback is the path to
stability.  -- Ben Warren 4baa6f5c.5060...@gmail.com
--
DENX Software Engineering GmbH,  MD: Wolfgang Denk  Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: d...@denx.de
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] *** Warning - bad CRC, using default environment

2010-05-18 Thread anup behare

Stefan,



I don't want to change the behavior and I can't use
CONFIG_ENV_IS_NOWHERE because we may change the environment variable and
save it.

Here my intention was to remove the warning runtime.



~Anup


On Tue, May 18, 2010 at 1:25 PM, Stefan Roese s...@denx.de wrote:

  On Tuesday 18 May 2010 09:11:16 anup behare wrote:
  While using u-boot for ppc440 based board we are getting *** Warning -
 bad
  CRC, using default environment message.
  On denx site we came to know that message is printed because the flash
  sector or ERPROM containing the environment variables has never been
  initialized yet.
  Is there any fix to remove this warning  message without passing the
  saveenv command on u-boot prompt?

 No, these is no fix, since this is not a bug but a desired feature.

 Why do you want to change this behaviour? Don't you have any environment
 storage area at all? Then you should define CONFIG_ENV_IS_NOWHERE in your
 board config header.

 Cheers,
 Stefan

 --
 DENX Software Engineering GmbH,  MD: Wolfgang Denk  Detlev Zundel
 HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
 Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: off...@denx.de

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] *** Warning - bad CRC, using default environment

2010-05-18 Thread Stefan Roese

On Tuesday 18 May 2010 11:12:26 anup behare wrote:
 I don't want to change the behavior and I can't use
 CONFIG_ENV_IS_NOWHERE because we may change the environment variable and
 save it.

And this usually happens upon board bring-up and/or factory testing. So in the 
normal use-case this warning will not be seen.
 
 Here my intention was to remove the warning runtime.

Why?

Cheers,
Stefan

--
DENX Software Engineering GmbH,  MD: Wolfgang Denk  Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: off...@denx.de
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] CONFIG_SYS_LINUX_LOWMEM_MAX_SIZE

2010-05-18 Thread anup behare

Hi  Stefan,


My intention was only to remove this warning.

My Linux is booting correctly and it is not causing any trouble but I
observed WARNING: adjusting available memory to 0x3000 on u-boot
console.

I have couple of question here with 768MB:

1. Is that mean u-boot will use only 768MB DDR?

2. What about kernel will it use complete DDR or will work with 768MB only?

3. Means we can’t remove this warning and this warning will come for DDR
more than 768MB?



~Anup


On Tue, May 18, 2010 at 1:37 PM, Stefan Roese s...@denx.de wrote:

 Hi Anup,

 On Tuesday 18 May 2010 09:03:25 anup behare wrote:
  We are using taishan based board having 1GB DDR.
  In u-boot code we found that CONFIG_SYS_LINUX_LOWMEM_MAX_SIZE is set to
  768MB hence if (size  bootm_size) condition becomes true and u-boot
  throw WARNING: adjusting available memory to 0x3000 message on
  console.
 
  Let me know will it possible to set CONFIG_SYS_LINUX_LOWMEM_MAX_SIZE to
 1GB
  or is there any fix for above warning message?

 Linux lowmem size is 768MB for PowerPC. Loading at a higher address
 results
 in a non-booting Linux kernel. So this warning makes sense and it's not
 possible to load to 1GB.

 Why do you want to change this? Does this cause you any troubles? Is Linux
 not
 booting correctly? I don't see what you would gain by loading to 1GB.

 Cheers,
 Stefan

 --
 DENX Software Engineering GmbH,  MD: Wolfgang Denk  Detlev Zundel
 HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
 Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: off...@denx.de

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] *** Warning - bad CRC, using default environment

2010-05-18 Thread anup behare

I removing the console warning and this is one of the warning.

On Tue, May 18, 2010 at 2:53 PM, Stefan Roese s...@denx.de wrote:

 On Tuesday 18 May 2010 11:12:26 anup behare wrote:
  I don't want to change the behavior and I can't use
  CONFIG_ENV_IS_NOWHERE because we may change the environment variable and
  save it.

 And this usually happens upon board bring-up and/or factory testing. So in
 the
 normal use-case this warning will not be seen.

  Here my intention was to remove the warning runtime.

 Why?

 Cheers,
 Stefan

 --
 DENX Software Engineering GmbH,  MD: Wolfgang Denk  Detlev Zundel
 HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
 Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: off...@denx.de

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] CONFIG_SYS_LINUX_LOWMEM_MAX_SIZE

2010-05-18 Thread Stefan Roese

Hi Anup,

On Tuesday 18 May 2010 11:24:42 anup behare wrote:
 My intention was only to remove this warning.

Perhaps it makes sense, to change this WARNUNG: to NOTE:. I suggest you 
send a patch for this and we might accept it.
 
 My Linux is booting correctly and it is not causing any trouble but I
 observed WARNING: adjusting available memory to 0x3000 on u-boot
 console.
 
 I have couple of question here with 768MB:
 
 1. Is that mean u-boot will use only 768MB DDR?

No.
 
 2. What about kernel will it use complete DDR or will work with
 768MB only?

That depends on your kernel configuration. For more than 768MB (lowmem) you 
need to enable highmem support of course.
 
 3. Means we can’t remove this warning and this warning will come for DDR
 more than 768MB?

Yes. But we might change the text from WARNING to NOTE or something 
like this (see above).

Cheers,
Stefan

--
DENX Software Engineering GmbH,  MD: Wolfgang Denk  Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: off...@denx.de
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Re: [U-Boot] [PATCH] Improve DaVinci SPI speed

2010-05-18 Thread Nori, Sekhar


Hi Delio,

On Thu, May 13, 2010 at 18:27:51, Delio Brignoli wrote:
 Reduce the number of reads per byte transferred on the BUF register from 2 to 
 1 and
 take advantage of the TX buffer in the SPI module.

The patch looks good to me.

Can you please publish some sort of numbers in the
patch description indicating the performance improvement
achieved?

A minor nit below:


 Signed-off-by: Delio Brignoli dbrign...@audioscience.com
 ---
  drivers/spi/davinci_spi.c |   67 +++-
  1 files changed, 35 insertions(+), 32 deletions(-)

 diff --git a/drivers/spi/davinci_spi.c b/drivers/spi/davinci_spi.c
 index 60ba007..b4a74de 100644
 --- a/drivers/spi/davinci_spi.c
 +++ b/drivers/spi/davinci_spi.c
 @@ -131,6 +131,7 @@ int spi_xfer(struct spi_slave *slave, unsigned int bitlen,
  {

[...]

 + /* write to DAT1 is required to keep the serial 
 transfer going */
 + /* we just terminate when we reach the end */
 + if((o_cnt == (len -1))  (flags  SPI_XFER_END)) {

Please include a space before the '-'

Thanks,
Sekhar

___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

42 matches

Mail list logo