Minkyu Kang 쓴 글:
> Dear Seunghyeon Rhee,
>
> 2009/11/28 "Seunghyeon Rhee (이승현)" :
>
>> The MSB of DMC1_MEM_CFG can be set to '1' for separate CKE control
>> for S3C6400. In the configuration of SMDK6400, however, two 16-bit
>> mDDR (SAMSUNG K4X51163) chips are used in parallel to form 32-bit
>>
Dear Seunghyeon Rhee,
2009/11/28 "Seunghyeon Rhee (이승현)" :
> The MSB of DMC1_MEM_CFG can be set to '1' for separate CKE control
> for S3C6400. In the configuration of SMDK6400, however, two 16-bit
> mDDR (SAMSUNG K4X51163) chips are used in parallel to form 32-bit
> memory bus and there is no need
Hi Stefan,
On Tue, Dec 1, 2009 at 11:25 PM, Stefan Roese wrote:
>
> This approach has multiple advantages:
>
> - Multiple file systems will be usable (FAT, EXT2 etc.)
> - Multiple MTD devices will be supported (NOR, NAND etc.)
>
>
I agree with you.
I though this is supported(and Wolfgang also t
On Tue, Dec 01, 2009 at 02:05:55PM +0100, Daniel Hobi wrote:
> Depending on offset, flash size and the number of bad blocks,
> get_len_incl_bad may return a too small value which may lead to:
>
> 1) If there are no bad blocks, nand_{read,write}_skip_bad chooses the
> bad block aware read/write cod
Paulraj, Sandeep wrote:
>>> +At this point of time it appears as if the entire common folder
>>> +needs to be updated with 64 bit values.
>> Yeah... If you want to put a concise note about this here, I'll add it,
>> though an actual bug tracking system would be nice. :-)
>
> Again let me know wha
>
> On Tue, Dec 01, 2009 at 01:06:07PM -0500, s-paul...@ti.com wrote:
> > +MTD NAND 64 bit support:
> > +
> > +
> > +The MTD NAND infrastructure in U-Boot(until release 2009.11) used only
> > +32 bit values to represent device size. As a result of which if we use
> > +a N
On Tue, Dec 01, 2009 at 01:06:07PM -0500, s-paul...@ti.com wrote:
> +MTD NAND 64 bit support:
> +
> +
> +The MTD NAND infrastructure in U-Boot(until release 2009.11) used only
> +32 bit values to represent device size. As a result of which if we use
> +a NAND device of size
Paulraj, Sandeep wrote:
>> Is it possible that there could be a race, whereby the hardware finishes
>> before you read NANDFSR for the first time, and thus you never see it be
>> greater than 3?
>
> There are other check conditions after this check condition in the driver.
> If we never see the co
> > From: Sandeep Paulraj
> >
> > There was a bug in the 4 bit ECC calculation routine
> > in the DaVinci NAND driver. This becomes prominent
> > when we use 4K page size NAND devices.
> > This is a fix for the issue.
> >
> > Signed-off-by: Sandeep Paulraj
> > ---
> > drivers/mtd/nand/davinci_n
On Tue, Dec 01, 2009 at 05:24:59PM -0500, s-paul...@ti.com wrote:
> From: Sandeep Paulraj
>
> There was a bug in the 4 bit ECC calculation routine
> in the DaVinci NAND driver. This becomes prominent
> when we use 4K page size NAND devices.
> This is a fix for the issue.
>
> Signed-off-by: Sande
From: Sandeep Paulraj
There was a bug in the 4 bit ECC calculation routine
in the DaVinci NAND driver. This becomes prominent
when we use 4K page size NAND devices.
This is a fix for the issue.
Signed-off-by: Sandeep Paulraj
---
drivers/mtd/nand/davinci_nand.c | 11 +++
1 files chang
Dear Jimmy Shergill,
In message you
wrote:
>
> I am a new user of U-boot and Linux. Please bear with me. I have Atmel
> AT91SAM9263-EK (ARM based) and have U-boot 1.3.4 running on it. Currently
> U-boot, Linux Kernel and jffs2 root filesystem, all are in NAND flash and
> work fine. We need to b
Jimmy Shergill wrote:
> Hello All,
>
> I am a new user of U-boot and Linux. Please bear with me. I have Atmel
> AT91SAM9263-EK (ARM based) and have U-boot 1.3.4 running on it. Currently
> U-boot, Linux Kernel and jffs2 root filesystem, all are in NAND flash and
> work fine. We need to boot the eva
Dear Fred Fan,
In message <2f495dc80912010844h6b4aa1e4i4588f808384b6...@mail.gmail.com> you
wrote:
>
> I almost fixed all of your comments.
>By some of them I can not fix them now.
> 1) Copyright block. It defined freescale other team. I can not change them
> directly.
I see. We will h
Hello All,
I am a new user of U-boot and Linux. Please bear with me. I have Atmel
AT91SAM9263-EK (ARM based) and have U-boot 1.3.4 running on it. Currently
U-boot, Linux Kernel and jffs2 root filesystem, all are in NAND flash and
work fine. We need to boot the evaluation kit from SD Card.
1. Does
Dear J.Hwan.Kim,
> Hi, everyone
>
> I'm trying to connect ethernet with AT91SAM9260.
> My board uses DM9161A as a ethernet transceiver.
>
> The u-boot ethernet initialization routine runs auto-negotiation,
> it works fine. Ethernet controller of AT91SAM9260
> (MACB0) receives Auto negotiation c
This patch adds support for the LaCie ED Mini V2 product
which is based on the Marvell Orion5x SoC.
Current support is limited to console and Flash.
Flash support uses LEGACY as the Macronix 29LV400
used on ED Mini V2 is not 100% CFI compliant.
Signed-off-by: Albert Aribaud
---
MAINTAINERS
This patch adds support for the Marvell Orion5x SoC.
It has no use alone, and must be followed by a patch
to add Orion5x support for serial, then support for
the ED Mini V2, an Orion5x-based product from LaCie.
Signed-off-by: Albert Aribaud
---
V1 of the patch was monolithic
V2 contains a number
This patch provides access to the 16550-compatible
serial device of the Orion5x SoC.
Signed-off-by: Albert Aribaud
---
drivers/serial/serial.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/drivers/serial/serial.c b/drivers/serial/serial.c
index dd5f332..18686a2 10064
On Tuesday 01 December 2009 07:56:45 Marcos Cunha wrote:
> Is it possible to use the SPI controller working with MMC driver to
> control a SDCARD?
search the mailing list for a driver
-mike
signature.asc
Description: This is a digitally signed message part.
__
Nick Thompson wrote:
> On 01/12/09 10:13, Nick Thompson wrote:
>> On 01/12/09 00:55, Scott Wood wrote:
>
>>> This change will break drivers that support large page and use the
>>> default read_page functions, but do not implement cmd_ctrl (they replace
>>> cmdfunc instead). This includes fsl_el
Nick Thompson wrote:
> I could put in a CONFIG_NAND_NO_LARGE_PAGE as well, but since small
> page devices are EOL now I was only looking to make it easier to
> remove legacy code (a bit like the Museum IDs in nand_ids.c).
I don't think small page support is going away any time soon.
>> Does it re
To update the real memory size in the memory node on the
uc101 and mucmc52 boards call fdt_fixup_memory() in
ft_board_setup().
Signed-off-by: Heiko Schocher
---
board/mucmc52/mucmc52.c |2 ++
board/uc101/uc101.c |2 ++
2 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/bo
From: Sandeep Paulraj
This patch updates the README for NAND.
There were some good updates made to the driver.
Signed-off-by: Sandeep Paulraj
---
doc/README.nand | 42 --
1 files changed, 40 insertions(+), 2 deletions(-)
diff --git a/doc/README.nand b
Dear wolfgang,
I almost fixed all of your comments.
By some of them I can not fix them now.
1) Copyright block. It defined freescale other team. I can not change them
directly.
2) iomux module can not use C structure to access registers. Because
register has
encoded in to pin defin
Two later additions to the Configuration Option section unfortunately
split the description of Show boot progress and the list of its call outs.
Signed-off-by: Detlev Zundel
---
README | 40
1 files changed, 20 insertions(+), 20 deletions(-)
diff --git
> Could the macros defined in apollo.h also be defined in the
> other target board's config file ?
I don't think so (my board is one of the affected ones).
The macros are CONFIG_ENV_ADDR_FLEX and CONFIG_ENV_SIZE_FLEX . I just
don't have the flex device.
In the commit that introduced the problem,
On Tue, Dec 1, 2009 at 4:24 PM, Tom wrote:
> Grazvydas Ignotas wrote:
>>
>> Not all boards have both LEDs hooked, so enabling both on
>> boards with single LED will just waste power.
>>
>
> This looks like a pandora specific change.
> Please say something like, "For Pandora, only 1 led is required
apgmoorthy wrote:
> Hi Tom,
>
>
> Moving these Macro definitions to "include/linux/mtd/onenand.h" looks more
> viable.
> I can send across the patch. Please comment.
>
Could the macros defined in apollo.h also be defined in the
other target board's config file ?
Thank you for looking into
Wolfgang Denk wrote:
> Dear Tom,
>
>>
>> Tom Rix (3):
>>ARM Update mach-types.h
>>ARM Update mach-types
>>ARM Update mach-types
>
>
> Why is this 3 commits? One should be enough...
>
I updated the mach-types 3 times.
I am updating about once a month or when required
Hi Tom,
Amul is out-of-office for sometime.
Excuse us for the delay.
>>In rebasing arm/next against u-boot/next.
>>There is a general error with targets that use onenand.
>>This includes the targets
>>nk8815_onenand
>>omap3_evm
>>smdkc100
>>I believe the error is from
>>commit c758e947aa7d39a2
Hi,
sorry for jumping in so late, but Wolfgang just broughtthis thread to my
attention. So here are my ideas and comments to your approach/patch:
> > * Which command can do this? (fatload seems can not because the
> > interface is not known)
> > * From which verion u-boot supports this featu
Grazvydas Ignotas wrote:
> Not all boards have both LEDs hooked, so enabling both on
> boards with single LED will just waste power.
>
This looks like a pandora specific change.
Please say something like, "For Pandora, only 1 led is required.. "
In some cases, the twl4030 led is the only led for
Depending on offset, flash size and the number of bad blocks,
get_len_incl_bad may return a too small value which may lead to:
1) If there are no bad blocks, nand_{read,write}_skip_bad chooses the
bad block aware read/write code. This may hurt performance, but does
not have any adverse effects.
2
Hi,
Is it possible to use the SPI controller working with MMC driver to
control a SDCARD?
Is that the best way?
Thanks in advance,
Marcos Cunha
Electrical Engineer
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-b
Thank you very much for your honest answer...
2009/12/1 Detlev Zundel :
> Hello Frédéric,
>
>> Thanks for you answer. How could I do a port to that board?
>
> Look into the README, search for "Ports to New Hardware". Ready the
> schematics for the board, datasheets of the vital components on it
anupbeh...@gmail.com wrote:
> Hi Jerry,
>
> Thanks for the information.
>
> Please find my understanding about dts:
> 1. I will have to create board specific *.dts file.
Yes. You should start with one from the linux source tree that matches
your essential hardware as closely as possible. Get
On 01/12/09 10:13, Nick Thompson wrote:
> On 01/12/09 00:55, Scott Wood wrote:
>> This change will break drivers that support large page and use the
>> default read_page functions, but do not implement cmd_ctrl (they replace
>> cmdfunc instead). This includes fsl_elbc_nand, mxc_nand, and
>> mp
Dear Tom,
In message <4b131a4d.1000...@windriver.com> you wrote:
> Wolfgang,
> I have rebased the arm/next against your next branch.
> The result is in arm/next-sync and arm/next
> Either is fine if you pull soon.
> Else use next-sync.
>
> The outstanding issues with arm/next are
> overo and beag
Hello Frédéric,
> Thanks for you answer. How could I do a port to that board?
Look into the README, search for "Ports to New Hardware". Ready the
schematics for the board, datasheets of the vital components on it (SoC
and RAM come to mind), warm up your editor and JTAG debugger and start
hackin
Thanks for you answer. How could I do a port to that board?
regards,
2009/12/1 Detlev Zundel :
> Hi Frédéric,
>
>> I got a KAMIO-1251 board equipped with a MIPS AU1250 CPU. I would
>> like to build U-BOOT for that board, is it possible?
>
> It is possible, but in mainline U-Boot the board is no
Dear Stefan Roese,
In message <200911251100.05463...@denx.de> you wrote:
> Hi Wolfgang,
>
> please pull this forgotten patch.
>
> Thanks.
>
> The following changes since commit 2f6f67da1b98b6d1dad2d80bc4e472c3bff3cd5a:
> Wolfgang Denk (1):
> Merge branch 'next' of git://www.denx.de/gi
Hi Frédéric,
> I got a KAMIO-1251 board equipped with a MIPS AU1250 CPU. I would
> like to build U-BOOT for that board, is it possible?
It is possible, but in mainline U-Boot the board is not (yet)
supported. So in order to build U-Boot you would need to do a port to
the board first
Also i
Hi Wolfgang,
> Dear Joakim Tjernlund,
>
> In message
> you
> wrote:
>>
>> > Yes. And all boards that don't need it will suffer from the increased
>> > memory footprint.
>>
>> Sure, but I won't adding these extra call sites as an array of
>> fptrs also add size? Since the new function as smalle
On 01/12/09 00:55, Scott Wood wrote:
> Nick Thompson wrote:
>> Improve read performance from Large Page NAND devices.
>>
>> This patch employs the following concepts to produce a ~37% improvement in
>> oob_first read speed (on a 300MHz ARM9). The time for a mid-buffer 2k page
>> read is now 260us,
Dear Scott McNutt,
In message <4b0c6998.30...@psyent.com> you wrote:
> The following changes since commit fcffb680e77fcb48598d4a9944dbe2d4503170e0:
>Mike Frysinger (1):
> sf: fix stmicro offset setup while erasing
>
> are available in the git repository at:
>
>git://git.denx.de/
Dear Scott McNutt,
In message <4b0afd1c.6060...@psyent.com> you wrote:
>
> The linker scripts in examples/standalone are no longer
> necessary since STANDALONE_LOAD_ADDR covers the original
> purpose of the scripts.
...
> Content-Type: text/plain;
> name="nios2-lds.patch"
> Content-Transfer-Encod
47 matches
Mail list logo
