Hi nobuhiro san.
I'have gone ahead on my board, derived from rks7203.
Now the system boots and alse the NOR flash (mine is an SST) works properly.
If you like we can stay in touch for the development
Best regards
In data venerdì 16 luglio 2010 08:31:55, Nobuhiro Iwamatsu ha scritto:
: Hi,
Pls remove below warning
edminiv2.c: In function ‘board_init’:
edminiv2.c:93: warning: implicit declaration of function
‘mvsata_ide_initialize_port’
Regards..
Prafulla . ..
___
From: u-boot-boun...@lists.denx.de [u-boot-boun...@lists.denx.de] On Behalf Of
Hi Fabio,
On Thursday 15 July 2010 11:55:17 Fabio Giovagnini wrote:
In my experience the SST39VF6402B has become full compliant with CFI mtd
interface just few linux kernel ago. In linux 2.6.17 it was not.
I'm developing on
U-Boot 2010.06-rc2-07985-g53f7677-dirty (lug 15 2010 - 11:41:21)
I have a udisk(My MP3), which is fat32 format, and the fs block size is
4096(report by u-boot).
enable USB and FAT support for u-boot.
do usb start cause the system to restart. after looking into the u-boot
code, I find that the DEFAULT_SECTOR_SIZE in disk/part_dos.h is too
small(512) to fit a
sorry, typo in the title, it is 4096
On Mon, Jul 19, 2010 at 4:44 PM, wesley xie elelon...@gmail.com wrote:
I have a udisk(My MP3), which is fat32 format, and the fs block size is
4096(report by u-boot).
enable USB and FAT support for u-boot.
do usb start cause the system to restart. after
Hi,
I'm completely new here, but looking to ask what's the best way to send in a
patch for the Xilinx SP601 board?
I've got it working and tested on two separate boards, however a key point
is that I don't use the microblaze-generic functionality (just the
microblaze) since I found it power pc
or, may be we need to detect the buffer size in usb_stor_read, to prevent it
from out of range ?
On Mon, Jul 19, 2010 at 4:45 PM, wesley xie elelon...@gmail.com wrote:
sorry, typo in the title, it is 4096
On Mon, Jul 19, 2010 at 4:44 PM, wesley xie elelon...@gmail.com wrote:
I have a
I Stefan. I did teh following upgrade of the fileyou suggestied to me.
#define SST39VF6402B0x236c
...
#ifdef CONFIG_SYS_FLASH_LEGACY_4Mx16
{
.mfr_id = (u16)SST_MANUFACT,
.dev_id = SST39VF6402B,
.name = SST
On Monday 19 July 2010 11:04:34 Fabio Giovagnini wrote:
I Stefan. I did teh following upgrade of the fileyou suggestied to me.
#define SST39VF6402B 0x236c
...
#ifdef CONFIG_SYS_FLASH_LEGACY_4Mx16
{
.mfr_id = (u16)SST_MANUFACT,
.dev_id =
Hi Fabio,
(please keep the list on Cc).
On Monday 19 July 2010 11:27:50 Fabio Giovagnini wrote:
I do not think so about teh different regons.
I attach the datasheet I found on the net and I cannot find anythink about
two different regions for
SST39VF6402B
Maybe I'm wrong.
Yes, you are
Hi Rogan,
On Tuesday 13 July 2010 22:00:37 Rogan Dawes wrote:
I'm trying to add support for my D-Link DNS323 (Orion5x-based) to
U-Boot, building on the efforts of Albert Aribaud.
One place where I am struggling is with the detection of the flash chip.
The flash part is a 8 MB Spansion
Superfloppy format (in U-Boot called PBR) did not work for FAT32
due to several errors; some errors appaeared only in certain
configurations (like directories with more than 128 entries, etc.).
These patches are supposed to fix these issues.
Wolfgang Denk (5):
usb_storage.c: initialize
The device type was left uninitialized which caused later tests
against DEV_TYPE_UNKNOWN to fail. In the result, usb part would
attempt to print information about non-existent devices like this:
= usb part
print_part of 0
Partition Map for USB device 0 -- Partition
Superfloppy format (in U-Boot called PBR) did not work for FAT32 as
the file system type string is at a different location. Add support
for FAT32.
Signed-off-by: Wolfgang Denk w...@denx.de
---
disk/part_dos.c |4 +++-
disk/part_dos.h |3 ++-
fs/fat/fat.c|4 +++-
3 files changed,
The dots printed by common/usb_storage.c as progress meter corrupt the
output for example of fatls usb commands like this:
= fatls usb 0
. here
29 file.001
29 file.002
29 file.003
29 file.004
29 file.005
29 file.006
On FAT32, instead of fetching the cluster numbers from the FAT, the
code assumed (incorrectly) that the clusters for the root directory
were allocated contiguously. In the result, only the first cluster
could be accessed. At the typical cluster size of 8 sectors this
caused all accesses to files
- reformat
- throw out macros like FAT_DPRINT and FAT_DPRINT
- remove dead code
Signed-off-by: Wolfgang Denk w...@denx.de
---
common/cmd_fat.c | 210 ++
fs/fat/fat.c | 1167 +-
fs/fat/file.c| 14 +-
include/fat.h| 63
yaojin liu wrote:
hi:
dm9000a works as 16bit bus width. however, i have not seen any init code for
the dm355's chipselect.
and by default ,the cs1 is 8bit bus width at reset. how doew it work?
I think the setup is done by the UBL provided by TI. U-boot is a 3-rd
stage bootloader for DM355.
On 2010/07/19 11:34 AM, Stefan Roese wrote:
Hi Rogan,
Hi Stefan,
Thanks for responding.
On Tuesday 13 July 2010 22:00:37 Rogan Dawes wrote:
I'm trying to add support for my D-Link DNS323 (Orion5x-based) to
U-Boot, building on the efforts of Albert Aribaud.
One place where I am struggling
I supposed the list doesn't like the attachment.
Anyway I understand, now.
I'll make you know how I'll solve.
Thanks a lot and best regards
In data lunedì 19 luglio 2010 11:33:43, Stefan Roese ha scritto:
: Hi Fabio,
(please keep the list on Cc).
On Monday 19 July 2010 11:27:50 Fabio
Hi Rogan,
On Monday 19 July 2010 12:18:45 Rogan Dawes wrote:
How is your FLASH chip connected to your CPU? In 16bit wide mode (which
is more common)?
I have no idea. Do you have any suggestions how I can find out?
I don't suppose you have the schematics for this board?
If I do a normal
On 2010/07/19 12:49 PM, Stefan Roese wrote:
Hi Rogan,
On Monday 19 July 2010 12:18:45 Rogan Dawes wrote:
How is your FLASH chip connected to your CPU? In 16bit wide mode (which
is more common)?
I have no idea. Do you have any suggestions how I can find out?
I don't suppose you have the
Hi Daniel,
-Original Message-
From: Daniel Gorsulowski [mailto:daniel.gorsulow...@esd.eu]
Sent: 2010?7?16? 14:22
To: u-boot@lists.denx.de
Cc: Xu, Hong; Daniel Gorsulowski
Subject: [PATCH-V2 1/3] at91: Defined main clock frequency on
esd at91 boards
Autodetection is undesired
Hi Daniel,
-Original Message-
From: Daniel Gorsulowski [mailto:daniel.gorsulow...@esd.eu]
Sent: 2010?7?16? 14:23
To: u-boot@lists.denx.de
Cc: Xu, Hong; Daniel Gorsulowski
Subject: [PATCH-V2 3/3] at91: Enabeling USB host on meesc board
There was an redesign, so USB is available
Hi Daniel,
-Original Message-
From: Daniel Gorsulowski [mailto:daniel.gorsulow...@esd.eu]
Sent: 2010?7?16? 14:23
To: u-boot@lists.denx.de
Cc: Xu, Hong; Daniel Gorsulowski
Subject: [PATCH-V2 2/3] at91: Update meesc board to new SoC access
* convert meesc board to use c stucture
On Monday 19 July 2010 13:05:09 Rogan Dawes wrote:
If I do a normal md over the rest of the flash, I do see expected
strings from the U-Boot partition, and the kernel and ramdisk
partitions. i.e. not duplicated or anything like that. Not sure if that
answers your question at all?
No,
Remy,
Any comment on this patch set ?
Regards,
Ajay
He sent me an e-mail offline.
He is on vacation without Wifi and laptop.
Thanks for updating on this.
Regards,
Ajay
Sandeep
___
U-Boot mailing list
U-Boot@lists.denx.de
- nfs-options removed
- hda-sda changed
- mtd parts added
- loadaddress changed
- cmd-line length increased
- lcd stuff removed
- code cleanup
Signed-off-by: Klaus Heydeck heyd...@kieback-peter.de
---
- changes since v1:
- added comments from Wolfgang Denk
- fix Codingstyle issues
-
since commit 1384f3bb8a4f9066805b70c1418eda78ecb73fdd ethernet names
with spaces drop a
Warning: eth device name has a space!
message. This patch fix it for FEC ETHERNET devices found on
mpc512x, mpc5xxx, mpc8xx and mpc8220 boards.
Tested on the kup4k board.
Signed-off-by: Heiko Schocher
* convert meesc board to use c stucture SoC access
* change gpio access to at91_gpio syntax
* moved CONFIG_SYS_HZ below board and cpu defines (purely cosmetic)
Signed-off-by: Daniel Gorsulowski daniel.gorsulow...@esd.eu
---
v2: fixed copyright changing error according to Wolfgangs hint
v3:
On 2010/07/19 1:50 PM, Stefan Roese wrote:
This is quite odd, though.
DNS323B1 mw.w 0xff800555 00aa
.. never returns. It seems to hang up the board for some reason.
Ahh, unaligned 16bit access on ARM.
Please give these commands another try:
= mw.w ff800aaa 00aa
= mw.w ff800554
Using this define, a board can define an opimized RFDC value and use
the auto calibration code to tune the remaining DDR2 controller
calibration register.
Signed-off-by: Stefan Roese s...@denx.de
---
arch/powerpc/cpu/ppc4xx/4xx_ibm_ddr2_autocalib.c | 12
1 files changed, 12
This patch fixes some problems for the T3CORP board. Here the list
of the changes:
- Add 600-67 and 677 CPU frequency setting to chip_config
command
- Define CONFIG_DDR_RFDC_FIXED on t3corp:
While using the normal auto calibration code, sometimes values for
RFDC were picked (= T3) that
The Samsung K9LBG08UXD parts are 32Gbytes x 8 bits 3.3V parts with
the 0xD7 identifier. Add this to the list of known devices IDs.
Signed-off-by: Lei Wen lei...@marvell.com
---
drivers/mtd/nand/nand_ids.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git
Rebased version for this nand chip has one problem in detecting its
page size using in nand_base.c.
If we set page size 0 in nand_ids.c, we would get the calculation
result as page size 2048, while the true page size is 4096.
I think it is reasonable to set the 32Gigabit nand as 4k page by
On Monday 19 July 2010 14:18:37 Rogan Dawes wrote:
DNS323B1 mw.w ff800aaa 00aa
DNS323B1 mw.w ff800554 0055
DNS323B1 mw.w ff800aaa 0090
DNS323B1 md.w ff80
ff80:
ff800010:
This is the rigth config for such a FLASH chip
#ifdef CONFIG_SYS_FLASH_LEGACY_4Mx16
{
.mfr_id = (u16)SST_MANUFACT,
.dev_id = SST39VF6402B,
.name = SST 39VF6402B,
.uaddr = {
On Monday 19 July 2010 15:57:09 Fabio Giovagnini wrote:
This is the rigth config for such a FLASH chip
#ifdef CONFIG_SYS_FLASH_LEGACY_4Mx16
{
.mfr_id = (u16)SST_MANUFACT,
.dev_id = SST39VF6402B,
.name = SST
Hi All,
I have downloaded u-boot-2010.06.tar.bz2 from Denx website, then tried to
configure it, it didn't work, i used
# make omap3530_config
It says :
make: *** No rule to make target `omap3530_config'. Stop.
Then it did : cd /board/ti
It says :
beagle omap1510inn omap2420h4
On 2010/07/19 3:33 PM, Stefan Roese wrote:
Not really. I find it odd, that writing 0x9800 works and 0x0098 doesn't.
Perhaps the chip is connected in byte-mode after all? Not sure.
Do you know if and how the Linux MTD driver handles the NOR FLASH?
Cheers,
Stefan
Here is the setup code from
thanks，you are right, it really init the chip through UBL.
BUT, there is also one question:
DM9000a 's driver has 8 bit accessing function:
#define CONFIG_DM9000_BASE0x0400
#define DM9000_IOCONFIG_DM9000_BASE
#define DM9000_DATA(CONFIG_DM9000_BASE+2) // (BA1,it's the
Ok
Cheers
In data lunedì 19 luglio 2010 16:19:23, Stefan Roese ha scritto:
: On Monday 19 July 2010 15:57:09 Fabio Giovagnini wrote:
This is the rigth config for such a FLASH chip
#ifdef CONFIG_SYS_FLASH_LEGACY_4Mx16
{
.mfr_id = (u16)SST_MANUFACT,
Dne Po 19. července 2010 17:29:48 StephenPaulraj Chinnadurai-ERS,HCLTech
napsal(a):
Hello Marek,
Hope you are doing well.
I registered with U-Boot@lists.denx.de list last week and came to know
about activities of the group.
You should possibly CC this mail into u-boot mailing list too.
There somewhere in the linux-sh galaxy something like that
http://www.stlinux.com/u-boot/target-install?
Thanks a lot
In data venerdì 16 luglio 2010 08:31:55, Nobuhiro Iwamatsu ha scritto:
: Hi, Fabio.
2010/7/14 Fabio Giovagnini fabio.giovagn...@aurion-tech.com:
Hi nobuhiro san.
Is it
-Original Message-
From: Marek Vasut [mailto:marek.va...@gmail.com]
Sent: Monday, July 19, 2010 9:11 PM
To: StephenPaulraj Chinnadurai-ERS,HCLTech
Cc: u-boot@lists.denx.de
Subject: Re: FW: Need Your Help
Dne Po 19. července 2010 17:29:48 StephenPaulraj Chinnadurai-ERS,HCLTech
Dear =?UTF-8?B?IlhpYW5nZnUgTGl1KOWImOWQkeWvjCki?=,
In message 4c43c9a9.7020...@openmobilefree.net you wrote:
before I apply the new board patches. the MAKEALL compile 359 boards.
after I applied the new board patches. the MAKEALL still compile 359 boards.
Then you obviously missed to add
Dear =?UTF-8?B?IlhpYW5nZnUgTGl1KOWImOWQkeWvjCki?=,
In message 4c43cabb.3070...@openmobilefree.net you wrote:
in this file : example/standalone/mips.lds
it indicate compile example as BIG mips. but my device is LITTLE mips.
so I simply comment this line[1]. I found other boards compile fine.
Dear Stefan Roese,
In message 1279542253-27041-1-git-send-email...@denx.de you wrote:
Using this define, a board can define an opimized RFDC value and use
the auto calibration code to tune the remaining DDR2 controller
calibration register.
...
@@ -767,6 +767,13 @@ static u32
On Mon, 19 Jul 2010 14:13:53 +0200
Heiko Schocher h...@denx.de wrote:
+int fdt_set_node_and_value(void *blob,
+ char *nodename,
+ char *regname,
+ void *var,
+ int size)
+{
+
Dear Heiko Schocher,
In message 4c4441d1.7080...@denx.de you wrote:
since commit 1384f3bb8a4f9066805b70c1418eda78ecb73fdd ethernet names
with spaces drop a
Warning: eth device name has a space!
message. This patch fix it for FEC ETHERNET devices found on
mpc512x, mpc5xxx, mpc8xx and
Dear xiangfu,
In message 1279509256-4524-1-git-send-email-xian...@openmobilefree.net you
wrote:
in my Ben Nanonote board. there is no flash. I got a error
about no CONFIG_SYS_FLASH_BASE define. so I move this
line to #ifndef CONFIG_SYS_NO_FLASH
I have tested with MAKEALL. no warning or
Dear xiangfu,
In message 1279510479-5285-1-git-send-email-xian...@openmobilefree.net you
wrote:
From: Xiangfu Liu xian...@sharism.cc
Hi Wolfgang Denk
in my Ben Nanonote board. there is no flash. I got a error
about no CONFIG_SYS_FLASH_BASE define. so I move this
line to #ifndef
Wolfgang Denk wrote:
I always wondered why we need such a long (and slow to type) name. I
suggest we use this opportunity and change the name into a plain and
simple FEC resp. SCC and FCC ?
Then probably unify the rule even for other architectures. We have a
FEC_MXC, too, for Freescale's i.MX
Hi Stefano,
On 7/19/2010 12:11 PM, Stefano Babic wrote:
Wolfgang Denk wrote:
I always wondered why we need such a long (and slow to type) name. I
suggest we use this opportunity and change the name into a plain and
simple FEC resp. SCC and FCC ?
Then probably unify the rule even for other
Dear Stefano Babic,
In message 4c44a356.7090...@denx.de you wrote:
I always wondered why we need such a long (and slow to type) name. I
suggest we use this opportunity and change the name into a plain and
simple FEC resp. SCC and FCC ?
Then probably unify the rule even for other
On Mon, Jul 19, 2010 at 09:05:05PM +0800, Lei Wen wrote:
Rebased version for this nand chip has one problem in detecting its
page size using in nand_base.c.
If we set page size 0 in nand_ids.c, we would get the calculation
result as page size 2048, while the true page size is 4096.
Is the ID
- nfs-options removed
- hda-sda changed
- mtd parts added
- loadaddress changed
- cmd-line length increased
- lcd stuff removed
- code cleanup
Signed-off-by: Klaus Heydeck heyd...@kieback-peter.de
---
- changes since v1:
- added comments from Wolfgang Denk
- fix Codingstyle issues
-
Signed-off-by: Heiko Schocher h...@denx.de
---
- changes since v1
- rebased against current mainline
- fix printf output
- changes since v2
added comments from Scott Wood
removed ft_blob_update() complete, because fixups are done in
cpu specific code.
board/kup/kup4k/kup4k.c | 11
since commit 1384f3bb8a4f9066805b70c1418eda78ecb73fdd ethernet names
with spaces drop a
Warning: eth device name has a space!
message. This patch fix it for:
- FEC ETHERNET devices found on
mpc512x, mpc5xxx, mpc8xx and mpc8220 boards.
renamed to FEC.
- SCC ETHERNET devices found on
Dear Heiko Schocher,
In message 4c44c8f9.6020...@denx.de you wrote:
since commit 1384f3bb8a4f9066805b70c1418eda78ecb73fdd ethernet names
with spaces drop a
Warning: eth device name has a space!
message. This patch fix it for:
- FEC ETHERNET devices found on
mpc512x, mpc5xxx, mpc8xx
Hi Heiko,
On 7/19/2010 3:57 PM, Wolfgang Denk wrote:
Dear Heiko Schocher,
In message4c44c8f9.6020...@denx.de you wrote:
since commit 1384f3bb8a4f9066805b70c1418eda78ecb73fdd ethernet names
with spaces drop a
Warning: eth device name has a space!
message. This patch fix it for:
- FEC
On Sat, 17 Jul 2010 21:45:48 +0200
Wolfgang Denk w...@denx.de wrote:
- It would be nice if we could add wildcard support for environment
variables; this is needed for variable name auto-completion,
but it would also be nice to be able to say printenv ip* or
printenv *addr*
you were
On Tue, Jul 20, 2010 at 4:22 AM, Scott Wood scottw...@freescale.com wrote:
On Mon, Jul 19, 2010 at 09:05:05PM +0800, Lei Wen wrote:
Rebased version for this nand chip has one problem in detecting its
page size using in nand_base.c.
If we set page size 0 in nand_ids.c, we would get the
Hi Wolfgang Denk
On 07/20/2010 01:45 AM, Wolfgang Denk wrote:
Dear =?UTF-8?B?IlhpYW5nZnUgTGl1KOWImOWQkeWvjCki?=,
In message4c43c9a9.7020...@openmobilefree.net you wrote:
before I apply the new board patches. the MAKEALL compile 359 boards.
after I applied the new board patches. the MAKEALL
oh. very sorry about the same message.
the git send-emails give me some error.
so I thought the email don't sended.
thanks for let me know :)
On 07/20/2010 02:56 AM, Wolfgang Denk wrote:
Dear xiangfu,
In message1279510479-5285-1-git-send-email-xian...@openmobilefree.net you
wrote:
From:
Dear Kim Phillips,
In message 20100719193356.a02add7e.kim.phill...@freescale.com you wrote:
+++ b/arch/powerpc/cpu/mpc83xx/acr.c
@@ -0,0 +1,29 @@
+/*
+ * Copyright (C) 2010 Freescale Semiconductor, Inc.
+ *
+ * See file CREDITS for list of people who contributed to this
+ * project.
+ *
After discussion on the ML it is suggested to drop unrequired
and not useful characters from the device name.
This patch changes the name for the fec_mxc driver from
FEC_MXC to FEC.
Signed-off-by: Stefano Babic sba...@denx.de
---
drivers/net/fec_mxc.c |2 +-
1 files changed, 1 insertions(+),
67 matches
Mail list logo
