Aha!
It seems like the root cause of this problem:
http://article.gmane.org/gmane.comp.boot-loaders.u-boot/53025/match=nasty+gunzip+problem+mpc8313e+rdb
As a MPC8313E(-RDB) user I'm happy no more checkstops will occur
for some kernels. I'm even more happy I took over the BAT settings
from MPC8315
Currently the mtdparts commands are included in the jffs2 command support.
This doesn't make sense anymore since other commands (e.g. UBI) use this
infrastructure as well now. This patch separates the mtdparts commands from
the jffs2 commands making it possible to only select mtdparts when no JFFS2
On Wednesday 18 March 2009, Kazuaki Ichinohe wrote:
> U-boot version: u-boot-2009.01
> boot log is the following.
>
> U-Boot 2009.01 ( 3譛 18 2009 - 09:38:17)
>
> ・PU: AMCC PowerPC 460EX Rev. A at 600 MHz (PLB=200, OPB=100, EBC=100 MHz)
> Security/Kasumi support
> Bootstrap Option
Stefan Roese wrote:
> On Wednesday 18 March 2009, Kazuaki Ichinohe wrote:
>
>> U-boot version: u-boot-2009.01
>> boot log is the following.
>>
>> U-Boot 2009.01 ( 3譛 18 2009 - 09:38:17)
>>
>> ・PU: AMCC PowerPC 460EX Rev. A at 600 MHz (PLB=200, OPB=100, EBC=100 MHz)
>> Security/Kasumi s
On Wednesday 18 March 2009, Felix Radensky wrote:
> >> Looks like you have ATI cards in both PCI-E slots and also SATA
> >> enabled. This cannot work, as SATA shares lines with x1 PCI-E
> >> slot on Canyonlands. Use J6 jumper to enable both PCI-E slots.
> >
> > No, it's PCI and not PCIe.
> >
> > B
Stefan Roese wrote:
> On Wednesday 18 March 2009, Felix Radensky wrote:
>
PCI: Bus Dev VenId DevId Class Int
00 06 1002 5960 0300 ff
00 06 1002 5940 0380 ff
PCIE1: link is not up.
PCIE1: initialization as root-complex failed
Video: ATI
On Wednesday 18 March 2009, Felix Radensky wrote:
> >> PCI: Bus Dev VenId DevId Class Int
> >> 00 06 1002 5960 0300 ff
> >> 00 06 1002 5940 0380 ff
> >> PCIE1: link is not up.
> >> PCIE1: initialization as root-complex failed
> >> Video: ATI Radeon video card (1002, 59
Hey All,
We are working on a Freescale Development Board (the MPC8315E-RDB). We have
used this board in the past with u-boot and it worked perfectly. However
now that we are trying to use it again - we seem to be having some trouble
getting the network working. We have tried the following with
With this patch non-uniform NOR FLASH chips (chips with multiple erase
regions) can be exported via the cfi-mtd layer and therefor used by UBI.
We select the largest sector size as erasesize. The cfi driver will make
sure that the smaller sectors are handled correctly.
Signed-off-by: Stefan Roese
On 22:41 Tue 17 Mar , Jesus Alvarez wrote:
> The AT91 Linux kernel patches for versions 2.6.27 or later use a separate
> atmel_nand.c driver that implements some OOB and ECC options that are not
> exactly the same as those in the standard kernel NAND driver (nand_base.c ,
> etc.). AT91 based bo
Another quick question. Since the Ethernet devices seem to both be working
on the physical layer (we can detect the cable plugged in) it must be a
software related problem. How does u-boot use the Ethernet chips, i.e. s to
awhere does it get driver to actually perform ping and tftp commands? I
k
Dear Louis Ruch,
In message <85a17cd50903180302x62c0f6c1u11e4876452608...@mail.gmail.com> you
wrote:
>
> We erased the flash on the board and every since then cannot get a ping
> reply from any deivce on our network, and we cannot ping the board itself.
...
> Since all the lights on the hub are o
Hi,
In U-boot-1.1.6 , when i did reset the NAND device is not found("No NAND
device found!!!") , if i Restart the board NAND device is detected . what
exactly the problem? any patch for this
board details
MPC8313ERDB board.
u-boot version 1.16
Thanks
Rudresh
--
View this message in context:
Hey Wolfgang,
Here is the printenv of my u-boot, it seems that the MAC addresses on the
development boards are set to a standard which does not change, since I got
a printenv from freescale where they have the ping working and they have the
same ethaddr as I do on my dev board:
Here is my printen
Hi Stefan, Kazuaki,
Stefan Roese wrote:
> On Wednesday 18 March 2009, Kazuaki Ichinohe wrote:
>> U-boot version: u-boot-2009.01
>> boot log is the following.
>>
>> U-Boot 2009.01 ( 3譛 18 2009 - 09:38:17)
>>
>> ・PU: AMCC PowerPC 460EX Rev. A at 600 MHz (PLB=200, OPB=100, EBC=100 MHz)
>> S
Hi Anatolij !
> Kazuaki, could you please change VIDEO_IO_OFFSET to 0xD080 and
> test again?
I'll try it.
Regards,
Kazuaki Ichinohe.
Anatolij Gustschin さんは書きました:
> Hi Stefan, Kazuaki,
>
> Stefan Roese wrote:
>> On Wednesday 18 March 2009, Kazuaki Ichinohe wrote:
>>> U-boot version: u-boo
Hi Anatolij, Stefan,
The exception was generated.
--
U-Boot 2009.01 ( 3月 18 2009 - 21:16:24)
CPU: AMCC PowerPC 460EX Rev. A at 800 MHz (PLB=200, OPB=100, EBC=100 MHz)
Security/Kasumi support
Bootstrap Option H - Boot ROM Location I2C (Addr 0x52)
Dear rudresh,
In message <22577501.p...@talk.nabble.com> you wrote:
>
> In U-boot-1.1.6 , when i did reset the NAND device is not found("No NAND
> device found!!!") , if i Restart the board NAND device is detected . what
> exactly the problem? any patch for this
U-Boot 1.1.6 is more than 2 year
> yes if they do not use the same ECC algo they will see the data corrupted
> and
> they will try to fix it
Thanks for your response. Yet I could not find CONFIG_ options in U-Boot
equivalent to the atmel_nand options in the kernel. It seems like the U-Boot
NAND writes and the kernel NAND writes
i tried with u-boot 1.3.0 its working fine, but the client required u-boot
1.1.6 version.
Thanks
Rudresh
wd wrote:
>
> Dear rudresh,
>
> In message <22577501.p...@talk.nabble.com> you wrote:
>>
>> In U-boot-1.1.6 , when i did reset the NAND device is not found("No NAND
>> device found!!!")
Mike Frysinger wrote:
> On Tuesday 17 March 2009 14:18:13 Scott Wood wrote:
>> Mike Frysinger wrote:
[snip]
>> I don't know of any amount of "nop" instructions that would be
>> architecturally guaranteed to avoid this -- they're no-ops, not syncs
>> (despite how some other architectures use them)
Hi Anatolij, Stefan,
The memory space is displayed in BAR2 of the PCI configuration space.
The video driver accesses this memory space and the exception is generated.
driver source: u-boot/drivers/video/ati_radeon_fb.c
function name: void *video_hw_init(void)
line : 760line
I attac
This patch includes the LPC2468 processor from NXP. Included is a
working board example.
Signed-off-by: Remco Poelstra
---
http://www.beryllium.net/~remco/u-boot.diff (144kb)
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/li
Dear rudresh,
In message <22578494.p...@talk.nabble.com> you wrote:
>
> i tried with u-boot 1.3.0 its working fine, but the client required u-boot
> 1.1.6 version.
So tell the client that you know how to fix the problem. The fix
consists in the update.
Best regards,
Wolfgang Denk
--
DENX So
Dear Remco Poelstra,
In message <49c0f362.50...@duran-audio.com> you wrote:
> This patch includes the LPC2468 processor from NXP. Included is a
> working board example.
>
> Signed-off-by: Remco Poelstra
> ---
> http://www.beryllium.net/~remco/u-boot.diff (144kb)
Please split this into a series
I fix this issue by removing fixup for MPC8313ERDB REVA board in
board\mpc8313erdb\mpc8313erdb.c, now its working fine.
int checkboard(void)
{
uint* led_ptr;
volatile immap_t *im = (immap_t *) CFG_IMMR;
puts("Board: Freescale MPC8313ERDB\n");
#if 0
led_ptr =
Jesus Alvarez micromint.com> writes:
>
> The AT91 Linux kernel patches for versions 2.6.27 or later use a separate
> atmel_nand.c driver that implements some OOB and ECC options that are not
> exactly the same as those in the standard kernel NAND driver (nand_base.c ,
> etc.). AT91 based boards
Kazuaki Ichinohe wrote:
> Hi Anatolij, Stefan,
>
> The memory space is displayed in BAR2 of the PCI configuration space.
> The video driver accesses this memory space and the exception is generated.
>
> driver source: u-boot/drivers/video/ati_radeon_fb.c
> function name: void *video_hw_init(voi
Dear Jesus Alvarez
> The AT91 Linux kernel patches for versions 2.6.27 or later use a separate
> atmel_nand.c driver that implements some OOB and ECC options that are not
> exactly the same as those in the standard kernel NAND driver (nand_base.c ,
> etc.). AT91 based boards can use the CONFIG_MTD_
Example board for LPC2468 support
Signed-off-by: Remco Poelstra
---
diff -upNr u-boot-orig/board/LPC2468/config.mk u-boot/board/LPC2468/config.mk
--- u-boot-orig/board/LPC2468/config.mk 1970-01-01 01:00:00.0 +0100
+++ u-boot/board/LPC2468/config.mk 2009-03-18 09:30:20.0 +0100
On Thu, Mar 12, 2009 at 02:49:06PM -0500, Peter Tyser wrote:
> - @rm -f
> $(obj)tools/{image.c,fdt.c,fdt_ro.c,fdt_rw.c,fdt_strerror.c,zlib.h}
> + @rm -f $(obj)tools/{image.c,fdt.c,fdt_ro.c,fdt_rw.c,fdt_strerror.c,}
That comma at the end looks like it would delete the tools directory, exce
On Wed, 2009-03-18 at 11:28 -0500, Scott Wood wrote:
> On Thu, Mar 12, 2009 at 02:49:06PM -0500, Peter Tyser wrote:
> > - @rm -f
> > $(obj)tools/{image.c,fdt.c,fdt_ro.c,fdt_rw.c,fdt_strerror.c,zlib.h}
> > + @rm -f $(obj)tools/{image.c,fdt.c,fdt_ro.c,fdt_rw.c,fdt_strerror.c,}
>
> That comma at
Dear Remco Poelstra,
In message <49c10b37.1070...@duran-audio.com> you wrote:
> This patch includes support for the LPC2468 processor from NXP.
>
> Signed-off-by: Remco Poelstra
General comment: There are lots of coding style issues: trailing
white space, incorrect brace style, lines t
Dear Peter Tyser,
In message <1237394171.13370.1059.ca...@localhost.localdomain> you wrote:
> On Wed, 2009-03-18 at 11:28 -0500, Scott Wood wrote:
> > On Thu, Mar 12, 2009 at 02:49:06PM -0500, Peter Tyser wrote:
> > > - @rm -f
> > > $(obj)tools/{image.c,fdt.c,fdt_ro.c,fdt_rw.c,fdt_strerror.c,zlib
From 9a7a9dfb1ed367b275bc19f7c40c98b63de75fb2 Mon Sep 17 00:00:00 2001
From: Richard Retanubun
Date: Wed, 18 Mar 2009 12:52:35 -0400
Subject: [PATCH] Update I2CFDR frequency divider 0x0E value from 192 to 204.
This patch changes the divider factor of 14 for I2CFDR.
Through empirical experiments
On Tue, Mar 17, 2009 at 01:30:38PM +0100, Wolfgang Denk wrote:
> Options if a board has (or uses) SPI flash and/or a SDCard and/or
> other things belong into the board config file. It makes no sense to
> provide long lists of make targets and then again long code to
> analyze these options in the t
On Mar 18, 2009, at 12:07 PM, Richard Retanubun wrote:
> From 9a7a9dfb1ed367b275bc19f7c40c98b63de75fb2 Mon Sep 17 00:00:00 2001
> From: Richard Retanubun
> Date: Wed, 18 Mar 2009 12:52:35 -0400
> Subject: [PATCH] Update I2CFDR frequency divider 0x0E value from 192
> to 204.
>
> This patch chan
>
> I'm considered about the impact of this change on PPC boards since they
> share the driver. I believe Timur had some experience with this. Not
> sure if the change should be #ifdef M68K or not.
it is already #ifdef M68k :)
___
U-Boot mailing lis
On Mar 18, 2009, at 1:04 PM, Richard Retanubun wrote:
>> I'm considered about the impact of this change on PPC boards since
>> they share the driver. I believe Timur had some experience with
>> this. Not sure if the change should be #ifdef M68K or not.
>
> it is already #ifdef M68k :)
than
Dear Scott Wood,
In message <20090318171535.gb3...@loki.buserror.net> you wrote:
>
> Unless I'm mistaken, those targets aren't for boards that merely *have* such
> things, but are trying to boot from the device in question, similar to the
> alternate configs for booting from NAND.
>
> > Assume ea
Dear Ladislav Michl,
In message <20090316222731.gb1...@localhost.localdomain> you wrote:
> Fix indentation broken by symbol renames. "Sort" driver related definitons.
>
> Signed-off-by: Ladislav Michl
Applied, thanks.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wo
Dear Ladislav Michl,
In message <20090316222932.gd1...@localhost.localdomain> you wrote:
> Use generic flash driver.
>
> Signed-off-by: Ladislav Michl
Does not apply to me:
Applying: NetStar: use generic flash driver
error: patch failed: include/configs/netstar.h:106
error: include/configs/net
Dear Heiko Schocher,
In message <49b8ad9b.7060...@denx.de> you wrote:
> with the new CONFIG_SYS_DELAYED_ICACHE config option, ICache
> is not enabled before code runs from RAM.
>
> Signed-off-by: Heiko Schocher
> ---
> README|5 +
> cpu/mpc8xx/start.S|2 +
Dear Heiko Schocher,
In message <49b8ad97@denx.de> you wrote:
> Size of one environment sector is 0x2.
>
> Signed-off-by: Heiko Schocher
> ---
> include/configs/mgcoge.h |2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/include/configs/mgcoge.h b/include/co
Dear Heiko Schocher,
In message <49b8ad9e.9060...@denx.de> you wrote:
> - added to keymile-common.h:
> - bootcount support
> - COMMAND HISTORY
> - CONFIG_AUTO_COMPLETE
> - CONFIG_SYS_FLASH_PROTECTION
> - JFFS2 support
> - CONFIG_VERSION_VARIABLE
> - extracted common I2C settings for al
Dear Heiko Schocher,
In message <49b8ada3.9060...@denx.de> you wrote:
> Signed-off-by: Heiko Schocher
> ---
> include/configs/mgsuvd.h | 57
> +-
> 1 files changed, 31 insertions(+), 26 deletions(-)
Applied, thanks.
Best regards,
Wolfgang Denk
-
Dear Heiko Schocher,
In message <49b8ada8.4010...@denx.de> you wrote:
> renaming the "mgsuvd" board port into "km8xx", because
> there come more similar boards from keymile.
> Compiling the mgsuvd board with "make mgsuvd_config"
> remains.
>
> Signed-off-by: Heiko Schocher
> ---
> Makefile
Dear Heiko Schocher,
In message <49b8adae.7010...@denx.de> you wrote:
> This patch adds support for the kmsupx4 board from Keymile,
> based on a Freescale MPC852T CPU
>
> - serial console on SMC1
> - 32 MB SDRAM
> - 32 MB NOR Flash
> - Ethernet over SCC3
> - I2C Bitbang
>
> Signed-off-by: Heiko
Dear Heiko Schocher,
In message <49bf44ed.1080...@denx.de> you wrote:
>
> I miss the following patchseries:
>
> http://lists.denx.de/pipermail/u-boot/2009-March/048916.html
Thanks for pointing out (I though this was for "next").
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH,
Dear Grzegorz Bernacki,
In message <12372808012245-git-send-email-...@semihalf.com> you wrote:
> Total5200 and digsy MTC use I2C port 2 pins as a ATA chip select.
> To avoid adding board-specific ifdefs to cpu/mpc5xxx/ide.c new
> define CONFIG_SYS_ATA_CS_ON_I2C2 was introduced. It is used by
> To
Dear Grzegorz Bernacki,
In message <12372808011109-git-send-email-...@semihalf.com> you wrote:
> This is the InterControl custom device based on the MPC5200B chip.
>
> Signed-off-by: Grzegorz Bernacki
> ---
> This patch depends on changes done under first patch in the series,
> because it uses d
Wolfgang Denk wrote:
> Dear Scott Wood,
>
> In message <20090318171535.gb3...@loki.buserror.net> you wrote:
>> Unless I'm mistaken, those targets aren't for boards that merely *have* such
>> things, but are trying to boot from the device in question, similar to the
>> alternate configs for booting
Dear Mike Frysinger,
In message <1235600980-15854-1-git-send-email-vap...@gentoo.org> you wrote:
> The smc911x driver changed the naming convention for its register funcs,
> so update the eeprom code accordingly.
>
> Signed-off-by: Mike Frysinger
> CC: Ben Warren
> ---
> examples/smc911x_eepro
Dear Stefan Roese,
In message <1236866146-22095-1-git-send-email...@denx.de> you wrote:
> --===2128501430==
>
> This patchset adds UBIFS read-only support to U-Boot. The following
> commands are implemented:
>
> - ubifsmount
> Mount an UBIFS volume
>
> - ubifsls
> List a directo
Dear Scott,
In message <49c1522d@freescale.com> you wrote:
>
> You'd rather tell the user they can't boot from a given device because
> it would clutter the makefile?
Select it in the board config file?
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk
Wolfgang Denk wrote:
> Dear Scott,
>
> In message <49c1522d@freescale.com> you wrote:
>> You'd rather tell the user they can't boot from a given device because
>> it would clutter the makefile?
>
> Select it in the board config file?
So the options are:
1. Make the user hand-edit the board
Dear Scott Wood,
I wrote:
> If you want to handle this typo through Makefile configuration, then at
> least write much shorter code.
s/typo/type of/
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D
Dear Scott Wood,
In message <49c15672.2000...@freescale.com> you wrote:
>
> So the options are:
> 1. Make the user hand-edit the board config file,
> 2. Duplicate the board config file, or
> 3. Put up with a little clutter in the makefile until a better system is
> put into place -- and hopefully
Dear Grzegorz Bernacki,
In message <12372808011109-git-send-email-...@semihalf.com> you wrote:
>
> Signed-off-by: Grzegorz Bernacki
> ---
> This patch depends on changes done under first patch in the series,
> because it uses define CONFIG_SYS_ATA_CS_ON_I2C2 introduded in there.
>
> MAKEALL
hi ,
I was wondering , is there any Discussion or document that describe the way
how I can Add a new device to u-Boot.
For example , I have two sequoa based, Custom design.
1) . I have an FPGA Device at the EBC port of EPx in the second design.
2) . In a second case, I have an FPGA Device as t
Hi,
I want to enable interrupts in ARM, Since the vectors are at fixed locations
like 0x and 0x, and physical memory starts from 0x5000 ,
this is only possible if vitual MMU is enabled, without this is it possible
like by using memory protection unit?.I am not sure can u plea
Hi Anatolij,
This is a problem that the memory space of BAR2 is inaccessible.
Even if the value of VIDEO_IO_OFFSET is changed, the problem is not solved.
It is a log that you demanded as follows.
-
U-Boot 2009.01 ( 3月 19 2009 - 11:17:08)
CPU: AMC
62 matches
Mail list logo
