Hi all !
I try to boot the kernel and rootfs using NFS!
Next is my u-boot env:
nfsboot=setenv bootargs root=/dev/nfs rw nfsroot=$serverip:$rootpath
ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netdev:off
console=$consoledev,$baudrate $othbootargs;tftp $loadaddr $bootfile;tftp
$fdtaddr $fdt
Hi all !
I try to boot the kernel and rootfs using NFS!
Next is my u-boot env:
nfsboot=setenv bootargs root=/dev/nfs rw nfsroot=$serverip:$rootpath
ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netdev:off
console=$consoledev,$baudrate $othbootargs;tftp $loadaddr $bootfile;tftp
$fdtaddr $fdt
2009/10/24 Cristian Axenie :
> Load address: 0x100
> Loading: *
> TFTP error: 'Access violation' (2)
Test this : mw 0x100 0x1234
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Ok !
And what do you exactly want to test with this, if I can write to the memory
?
The u-boot command returns sucessfully!
no problem with mw !
On Sat, Oct 24, 2009 at 11:57 AM, wilbur.chan wrote:
> 2009/10/24 Cristian Axenie :
> > Load address: 0x100
> > Loading: *
> > TFTP error: 'Access
Dear Cristian Axenie,
In message <9c789a000910240122j776b762dodbddb97a105c9...@mail.gmail.com> you
wrote:
>
> I try to boot the kernel and rootfs using NFS!
What exactly has this to do with NFS at all?
> TFTP from server 192.168.1.103; our IP address is 192.168.1.100
> Filename '/home/haustiq/d
>
> Alternatively, I have seen some unofficial u-boot ports for s3c24x0 cpu's that
> do support u-boot booting from NAND flash but I don't have the source code
> for them.
>
Kevin,
I think this[1] is the code you are talking about. I just give it a try
and it works like a charm when booting fro
On 24/10/2009 12:53, Gaye Abdoulaye Walsimou wrote:
>> Alternatively, I have seen some unofficial u-boot ports for s3c24x0 cpu's
>> that
>> do support u-boot booting from NAND flash but I don't have the source code
>> for them.
>>
> Kevin,
> I think this[1] is the code you are talking about.
Cristian Axenie wrote:
> Hi all !
>
> I try to boot the kernel and rootfs using NFS!
> Next is my u-boot env:
[snip]
> bootfile=/home/haustiq/development/uImage
Likely wrong (see below).
> My problem is that when I
>
> run bootcmd
>
> I get :
>
>
> Speed: 100, full duplex
> Using eTSEC0 de
On Sat, Oct 24, 2009 at 5:09 PM, Jerry Van Baren wrote:
> Cristian Axenie wrote:
>
>> Hi all !
>>
>> I try to boot the kernel and rootfs using NFS!
>> Next is my u-boot env:
>>
>
> [snip]
>
>
> bootfile=/home/haustiq/development/uImage
>>
>
> Likely wrong (see below).
>
>
> My problem is that wh
Cristian Axenie wrote:
> On Sat, Oct 24, 2009 at 5:09 PM, Jerry Van Baren wrote:
>
>> Cristian Axenie wrote:
>>
>>> Hi all !
[snip]
>> My problem is that when I
>>> run bootcmd
>>>
>>> I get :
>>>
>>> Speed: 100, full duplex
>>> Using eTSEC0 device
>>> TFTP from server 192.168.1.103; our IP add
5 is correct.
Here's an example:
rtt = 0x3:
esd_mode should be = 0x44:
esdmode = (0
| ((rtt & 0x4) << 7) /* rtt field is split */
| ((rtt & 0x2) << 5) /* rtt field is split */
| ((rtt & 0x1) << 2) /* rtt field is split */
On Oct 22, 2009, at 7:39 PM, Peter Tyser wrote:
> Add a new 'ecc' command to interact with the 85xx and 86xx DDR ECC
> registers. The 'ecc' command can inject data/ECC errors to simulate
> errors and provides an 'info' subcommand which displays ECC error
> information such as failure address, re
i use:
make ep7312_config
make all
then
在函数‘start_armboot’中：
/home/smile/u-boot-2009.08/lib_arm/board.c:428：对‘cs8900_get_enetaddr’未定义的引用
net/libnet.a(net.o)：在函数‘ArpRequest’中：
/home/smile/u-boot-2009.08/net/net.c:250：对‘eth_send’未定义的引用
net/libnet.a(net.o)：在函数‘NetStartAgain’中：
/home/smile/u-boo
Moved the mdio regs out of the tsec structure,and
provided different offsets for tsec base and mdio
base so that provision for etsec2.0 can be provided.
This patch helps in providing the support for etsec2.0
In etsec2.0, the MDIO register space and the etsec reg
space are different.
Also, moved t
1. Modified the tsec_mdio structure to include the new regs
2. Modified the MDIO_BASE_ADDR so that it will handle both
older version and new version of etsec.
Signed-off-by: Sandeep Gopalpet
---
include/asm-ppc/immap_85xx.h |7 ++-
include/configs/P1_P2_RDB.h |5 +
include/tsec.
Moved the mdio regs out of the tsec structure,and
provided different offsets for tsec base and mdio
base so that provision for etsec2.0 can be provided.
This patch helps in providing the support for etsec2.0
In etsec2.0, the MDIO register space and the etsec reg
space are different.
Also, moved t
1. Modified the tsec_mdio structure to include the new regs
2. Modified the MDIO_BASE_ADDR so that it will handle both
older version and new version of etsec.
Signed-off-by: Sandeep Gopalpet
---
include/asm-ppc/immap_85xx.h |7 ++-
include/configs/P1_P2_RDB.h |5 +
include/tsec.
Dear Cristian Axenie,
In message <9c789a000910240721x1789c1d9n3fefd3abd327e...@mail.gmail.com> you
wrote:
>
> But if I changed the directory to the one mentioned before in the
> /etc/inetd.conf and didn't used /tftpboot ?
In addition to all the excellent advice JvB already gave you just one
more
Dear Peter Tyser,
In message <1256258353-25589-1-git-send-email-pty...@xes-inc.com> you wrote:
> Add a new 'ecc' command to interact with the 85xx and 86xx DDR ECC
> registers. The 'ecc' command can inject data/ECC errors to simulate
> errors and provides an 'info' subcommand which displays ECC e
Dear Peter Tyser,
In message <1256259563-32725-1-git-send-email-pty...@xes-inc.com> you wrote:
> Previously, passing readline() or readline_into_buffer() a NULL 'prompt'
> parameter would result in puts() printing garbage when
> CONFIG_CMDLINE_EDITING was enabled.
What would be the situation when
Dear Peter Tyser,
In message <1256259563-32725-3-git-send-email-pty...@xes-inc.com> you wrote:
> If the 'buf' parameter is a non-0-length string, its contents will be
> edited. Previously, the initial value of 'buf' was ignored and the
> user entered its contents from scratch.
What is the purpos
I on behalf of my colleagues being senior staffs with a bank here in Spain need
your humble assistance
in repatriating some funds left behind by a late customer that died before, it
is declared unserviceable
within the next 30 days. I decided to contact you due to the urgency of this
transaction
Dear LakeAylwyn,
please make sure to post plain text only, using an internationally
well accepted character set (ASCII, ISO-8859).
In message you wrote:
>
> i use:
>
> make ep7312_config
> make all
Which tool chain are you using, and what is your setting of
CROSS_COMPILE ?
> then
>
> ÔÚº¯Êý
I on behalf of my colleagues being senior staffs with a bank here in Spain need
your humble assistance
in repatriating some funds left behind by a late customer that died before, it
is declared unserviceable
within the next 30 days. I decided to contact you due to the urgency of this
transaction
Wolfgang,
Please pull from u-boot-arm, master-sync branch.
The change from the v3 is to put Steve's network patch back
and to remove Nishanth's memory patch.
Tom
Here is the diff from v3 to v4 :
21c21
< Nishanth Menon (4):
---
> Nishanth Menon (3):
24d23
< OMAP3: Fix SDRC init
45c44
< St
Chris Isbell wrote:
> U-Boot 2009.08 fails to compile with the arm-eabi compiler (V4.1.0 and
> V4.3.1) when YAFFS2 support is enabled (CONFIG_YAFFS2 defined as 1). It
> reports undefined symbols. (JFFS2 support compiles successfully.)
>
> Having investigated, it appears that a work around is to cr
javier Martin wrote:
> Who can ack this patch?
> Is Fred Fan or Tom Rix?
>
This looked like a network patch, so it would go to Ben.
Tom
> Thank you.
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Dear Ben Warren,
In message <4adcb2ee.6000...@gmail.com> you wrote:
> Wolfgang,
>
> Please pull the net branch (master). This includes a patch that was
> somehow lost back in April. It's pretty low-risk.
>
> The following changes since commit f67066b6b0740b826ed862615c5ab022aaf4779a:
> Mike
Dear Kim Phillips,
In message <20091022102910.720e578c.kim.phill...@freescale.com> you wrote:
> On Sun, 18 Oct 2009 21:25:59 +0200
> Wolfgang Denk wrote:
>
> > > Kim Phillips (1):
> > > mpc83xx: mpc8313 - handle erratum IPIC1 (TSEC IRQ number swappage)
> >
> >
> > Sorry, but has this pa
Dear Kim Phillips,
In message <20091016173304.ca71eb5a.kim.phill...@freescale.com> you wrote:
> Wolfgang Denk,
>
> Please pull a fix for 8313 rev.2+ networking device trees and a minor
> consistency fix:
>
> The following changes since commit cd77dd109c4a439519a78c32eddc42bdebc7a61f:
> Wolfgan
Dear Stefan Roese,
In message <200910231620.05225...@denx.de> you wrote:
> Hi Wolfgang,
>
> please pull some fixes and last minute updates from ppc4xx. Thanks.
>
> The following changes since commit f67066b6b0740b826ed862615c5ab022aaf4779a:
> Mike Frysinger (1):
> envcrc: check return
Dear Kumar Gala,
In message <1256185791-5492-1-git-send-email-ga...@kernel.crashing.org> you
wrote:
> Its possible that we end up with a device tree that happens to be a
> particular size that after we call fdt_resize() we don't have any
> space left for the initrd mem_rsv.
>
> Fix this be addin
Dear Mike Frysinger,
In message <1255122764-20310-1-git-send-email-vap...@gentoo.org> you wrote:
> Some of the new spi flash files were missing explicit license lines.
>
> Signed-off-by: Mike Frysinger
> CC: Haavard Skinnemoen
> ---
> this needs Haavard's approval since he wrote/submitted the o
Dear Tom,
In message <4ae34731.5000...@windriver.com> you wrote:
> Wolfgang,
>
> Please pull from u-boot-arm, master-sync branch.
>
> The change from the v3 is to put Steve's network patch back
> and to remove Nishanth's memory patch.
>
> Tom
>
> Here is the diff from v3 to v4 :
>
> 21c21
> <
Nick Thompson wrote:
> Add initial support for DA8xx SoC's and the spectrum digital DA830 EVM board.
>
> DA8xx is similar to DaVinci devices, but has a differing memory map and
> updated peripherals. It is intended that DaVinci drivers will be modified in
> some way to support these differences.
>
Dear Stefan Roese,
In message <200910231124.45435...@denx.de> you wrote:
>
> On Friday 23 October 2009 10:52:38 Matthias Fuchs wrote:
> > These files were autogenerated by EPSON configuration tools.
> > This patch replaces the autogenerated file headers by the GPL
> > license notice.
> >
> > Thi
Dear Matthias Fuchs,
In message <200910231052.38213.matthias.fu...@esd.eu> you wrote:
> These files were autogenerated by EPSON configuration tools.
> This patch replaces the autogenerated file headers by the GPL
> license notice.
>
> This change is done with the explicit permission
> of Epson Re
On Sat, Oct 24, 2009 at 8:12 PM, Wolfgang Denk wrote:
> Dear Cristian Axenie,
>
> In message <9c789a000910240721x1789c1d9n3fefd3abd327e...@mail.gmail.com>
> you wrote:
> >
> > But if I changed the directory to the one mentioned before in the
> > /etc/inetd.conf and didn't used /tftpboot ?
>
> In
Kumar Gala wrote:
>
> On Oct 22, 2009, at 7:39 PM, Peter Tyser wrote:
>
>> Add a new 'ecc' command to interact with the 85xx and 86xx DDR ECC
>> registers. The 'ecc' command can inject data/ECC errors to simulate
>> errors and provides an 'info' subcommand which displays ECC error
>> information
Hi Wolfgang,
> In message <1256258353-25589-1-git-send-email-pty...@xes-inc.com> you wrote:
>> Add a new 'ecc' command to interact with the 85xx and 86xx DDR ECC
>> registers. The 'ecc' command can inject data/ECC errors to simulate
>> errors and provides an 'info' subcommand which displays ECC e
Dear Peter,
In message <4ae371e7.3000...@xes-inc.com> you wrote:
>
> 83xx, 85xx, and 86xx could all share an implementation I believe. I
> didn't integrate the 83xx in this patch because it seemed to have a
> different "goal" than the patch I submitted. The 83xx implementation
> supported a h
Wolfgang Denk wrote:
> Dear Peter Tyser,
>
> In message <1256259563-32725-1-git-send-email-pty...@xes-inc.com> you wrote:
>> Previously, passing readline() or readline_into_buffer() a NULL 'prompt'
>> parameter would result in puts() printing garbage when
>> CONFIG_CMDLINE_EDITING was enabled.
>
> In message <4ae371e7.3000...@xes-inc.com> you wrote:
>> 83xx, 85xx, and 86xx could all share an implementation I believe. I
>> didn't integrate the 83xx in this patch because it seemed to have a
>> different "goal" than the patch I submitted. The 83xx implementation
>> supported a high degre
Dear Peter Tyser,
In message <4ae373ab.6040...@xes-inc.com> you wrote:
>
> In this series, patches 1/2/4 are non-critical cleanup/fixes. I didn't
> plan on them get merged for the upcoming release, but I think they
> should get picked up at some point. Patches 3/5 add new features -
> basical
Wolfgang Denk wrote:
> Dear Peter Tyser,
>
> In message <1256259563-32725-3-git-send-email-pty...@xes-inc.com> you wrote:
>> If the 'buf' parameter is a non-0-length string, its contents will be
>> edited. Previously, the initial value of 'buf' was ignored and the
>> user entered its contents fro
Wolfgang Denk wrote:
> Dear Peter Tyser,
>
> In message <4ae373ab.6040...@xes-inc.com> you wrote:
>> In this series, patches 1/2/4 are non-critical cleanup/fixes. I didn't
>> plan on them get merged for the upcoming release, but I think they
>> should get picked up at some point. Patches 3/5 a
Dear Peter Tyser,
In message <4ae37708.7050...@xes-inc.com> you wrote:
>
> > I don't want to debate these. Actually I like the code.
>
> Fantastic!
Indeed :-)
> > And if you
> > could be so kind and write a little more about this background
> > information in the commit messages, I'm really tem
Nick Thompson wrote:
> Add new directory for da8xx cpu functions.
>
> Provides initial support for TI OMAP-L1x/DA8xx SoC devices.
> See http://www.ti.com
>
> Provides:
> Low level initialisation.
> System clock API.
> Timer control.
> System reset.
It looks like this patch is duplicating much o
>
> Nick Thompson wrote:
> > Add new directory for da8xx cpu functions.
> >
> > Provides initial support for TI OMAP-L1x/DA8xx SoC devices.
> > See http://www.ti.com
> >
> > Provides:
> > Low level initialisation.
> > System clock API.
> > Timer control.
> > System reset.
>
>
> It looks like this
Nick Thompson wrote:
> Add new directory for da8xx architecture includes.
>
> Provides initial support for TI OMAP-L1x/DA8xx SoC devices.
> See http://www.ti.com
>
> The DA8xx devices are similar to DaVinci devices but have a differing
> memory map and updated peripheral versions.
>
> Signed-off
Nick Thompson wrote:
> Add new directory for da830evm board
>
> Provides initial support for TI OMAP-L137/DA830 SoC devices on a Spectrum
> Digital EVM board. See http://www.spectrumdigital.com/
>
> Provides:
> Initial boot and configuration.
> Support for i2c.
> UART support (console).
>
> Sign
Nick Thompson wrote:
> Integrate DA830 EVM support into U-Boot.
>
> Provides initial support for TI OMAP-L137/DA830 SoC devices on a Spectrum
> Digital EVM board. See http://www.spectrumdigital.com/
>
> Signed-off-by: Nick Thompson
> ---
> Applies to u-boot-ti
>
> MAINTAINERS|
Paulraj, Sandeep wrote:
>
>> Nick Thompson wrote:
>>> Add new directory for da8xx cpu functions.
>>>
>>> Provides initial support for TI OMAP-L1x/DA8xx SoC devices.
>>> See http://www.ti.com
>>>
>>> Provides:
>>> Low level initialisation.
>>> System clock API.
>>> Timer control.
>>> System reset.
I have pushed an update to arm / next.
This used the mach-types.h from Russel's cur-git repo.
I did not see zoom3 there so I will need to update this again closer
to when I submit the board.
If you do not see that board you were looking for either,
let me know. I would rather pull this file from
On Saturday 24 October 2009 17:47:27 Peter Tyser wrote:
> Wolfgang Denk wrote:
> > Peter Tyser wrote:
> >> If the 'buf' parameter is a non-0-length string, its contents will be
> >> edited. Previously, the initial value of 'buf' was ignored and the
> >> user entered its contents from scratch.
> >
On Sat, Oct 24, 2009 at 11:35 AM, Tom wrote:
> javier Martin wrote:
>
>> Who can ack this patch?
>> Is Fred Fan or Tom Rix?
>>
>> This looked like a network patch, so it would go to Ben.
> Tom
>
> Yeah, this is in my jurisdiction. I'll take care of it this weekend.
regards,
Ben
___
56 matches
Mail list logo
