Thanks Ben.
I'll wait for more suggestions and re-generate the whole patch again.
Hope I do not bother you guys too much. It's my first time saying
something in this list. :-)
On Tue, Jul 29, 2008 at 12:57, Ben Warren <[EMAIL PROTECTED]> wrote:
> Hi Hong,
>
> Thanks for all the hard work. One mor
Hi Hong,
Thanks for all the hard work. One more thing...
> +#if defined(CONFIG_CMD_NET)
> +int board_eth_init(bd_t *bis)
> +{
> + return at91sam9_eth_initialize(bis);
> +}
> +#endif
Here's at91sam9_eth_initialize:
#if defined(CONFIG_MACB) && defined(CONFIG_CMD_NET)
void at91sam9_eth_init
> I have a copy of the Verilog code used in the BCSR
I took a closer look at the Verilog code. Searching
for the I/O port nBCSR_CS within the code shows that
it is synchronized through a single register to the 33MHz
clock (which comes from on-board oscillator, not the
processor) to generate the s
Wolfgang Ocker wrote:
> Use CFG_MIPS_TIMER_FREQ when computing the baudrate divisor
> on alchemy cpus.
>
> Signed-off-by: Wolfgang Ocker <[EMAIL PROTECTED]>
Thanks, I'll apply and push this out tonight. This patch should go in
the upcoming v1.3.4 final.
Shinya
> ---
> diff --git a/cpu/mips/a
Hi Dave,
> I believe it is timing issue.
> The BCSR read(#LOE) has not enough setup time.
> You may try the two solutions:
> (a) slow down local bus clock
> If you are using default configuration, the local bus clock is
> 66MHz. change the LCRR from div 4 to div 8 to make the local bus clock
>
On Tue, Jul 29, 2008 at 10:17, Hong Xu <[EMAIL PROTECTED]> wrote:
> From 8e7f74804f86c25639f4009ba14fd6c1affe5ee6 Mon Sep 17 00:00:00 2001
> From: Hong Xu <[EMAIL PROTECTED]>
> Date: Tue, 29 Jul 2008 09:23:47 +0800
> Subject: [PATCH 1/1] Add support for ATMEL AT91SAM9G20EK board.
>
> This patch add
>From 8e7f74804f86c25639f4009ba14fd6c1affe5ee6 Mon Sep 17 00:00:00 2001
From: Hong Xu <[EMAIL PROTECTED]>
Date: Tue, 29 Jul 2008 09:23:47 +0800
Subject: [PATCH 1/1] Add support for ATMEL AT91SAM9G20EK board.
This patch add support for ATMEL AT91SAM9G20EK board.
- Per J's request, this patch's base
On Sat, Jul 26, 2008 at 6:27 AM, Scott Wood <[EMAIL PROTECTED]> wrote:
> On Fri, Jul 25, 2008 at 04:23:34PM +0900, Kyungmin Park wrote:
>> +/*
>> + * Enumeration for NAND/OneNAND flash chip state
>> + */
>> +enum {
>> + FL_READY,
>> + FL_READING,
>> + FL_WRITING,
>> + FL_ERASING,
>>
Hi,
On Sat, Jul 26, 2008 at 6:21 AM, Scott Wood <[EMAIL PROTECTED]> wrote:
> On Fri, Jul 25, 2008 at 04:23:34PM +0900, Kyungmin Park wrote:
>> Use the common declaration in NAND/OneNAND state
>
> As previously requested, please base this patch against the testing
> branch of the u-boot-nand-flash
On Mon, Jul 28, 2008 at 12:16 PM, Ricardo Ribalda Delgado
<[EMAIL PROTECTED]> wrote:
> Hello Grant
>
> Thanks for your comment. The use for the ddr2 is just an example...
> I did developed it for that reason, but you can use it for anything
> else. I sent the patch just because I thought it will b
Add OneNAND IPL related files to gitignore
Signed-off-by: Kyungmin Park <[EMAIL PROTECTED]>
---
diff --git a/.gitignore b/.gitignore
index 89e96f5..96c1b4a 100644
--- a/.gitignore
+++ b/.gitignore
@@ -26,6 +26,8 @@
/u-boot.ldr
/u-boot.ldr.hex
/u-boot.ldr.srec
+/u-boot-onenand.bin
+/u-boot-flexo
On Mon, 23 Jun 2008 16:00:28 +0200
Marc Leeman <[EMAIL PROTECTED]> wrote:
> Since I moved to FDT (from the previous OF implementation), I get the
> following behaviour.
..
> However, the MAC addresses that are passed to the kernel are a mix of
> the hardcoded defaults and the ones retrieved from
On Mon, Jul 28, 2008 at 10:03:43PM +0200, Jean-Christophe PLAGNIOL-VILLARD
wrote:
>
> +
> > +static const struct sdram_config sdram_config = {
> > +.data_bits= SDRAM_DATA_16BIT,
> > +.row_bits= 13,
> > +.col_bits= 9,
> > +.bank_bits= 2,
> > +.cas= 3,
>
+
> +static const struct sdram_config sdram_config = {
> +.data_bits= SDRAM_DATA_16BIT,
> +.row_bits= 13,
> +.col_bits= 9,
> +.bank_bits= 2,
> +.cas= 3,
> +.twr= 2,
> +.trc= 6,
> +.trp= 2,
> +.trcd= 2,
> +
Hi Mark,
On Mon, Jul 28, 2008 at 12:32 PM, Mark Jackson <[EMAIL PROTECTED]> wrote:
> The MIMC200 board is based on Atmel's NGW100 dev kit,
> but with an extra 8MByte FLASH and 128KByte FRAM.
>
No need to put the stuff about board_eth_init() in the subject. Just
label this as [PATCH V2].
> +
Can someone with the appropriate access run git-update-server-info on
u-boot-nand-flash.git? Currently, it is impossible to clone this
repository via HTTP.
Ideally, this should run via a post-receive hook...
-Scott
-
This S
The MIMC200 board is based on Atmel's NGW100 dev kit,
but with an extra 8MByte FLASH and 128KByte FRAM.
---
CREDITS|4 +
MAINTAINERS|4 +
MAKEALL|1 +
Makefile |3 +
board/atmel/mimc200/Makefile
Kumar Gala wrote:
> On Jul 28, 2008, at 12:40 PM, Grant Likely wrote:
>> In principle I like the idea of having configuration retrieved from
>> the device tree blob, but the idea of reflashing the blob in the
>> context of u-boot scares me. In particular, if u-boot depends too
>> much on the pres
Ben Warren wrote:
> Uh, yeah. I like the idea of a central repo for hardware info, and
> the device tree concept is good. My point is that the syntax, while
> concise and exact, can be intimidating. Just look at the amount of
> traffic on the mailing lists of people that don't understand what al
Signed-off-by: Rafal Czubak <[EMAIL PROTECTED]>
Acked-by: Rafal Jaworowski <[EMAIL PROTECTED]>
---
api/api_storage.c| 29 ++---
api_examples/demo.c | 11 +++
include/api_public.h |1 +
3 files changed, 30 insertions(+), 11 deletions(-)
diff --git a/api
Signed-off-by: Rafal Czubak <[EMAIL PROTECTED]>
Acked-by: Rafal Jaworowski <[EMAIL PROTECTED]>
---
api_examples/demo.c | 50 --
1 files changed, 44 insertions(+), 6 deletions(-)
diff --git a/api_examples/demo.c b/api_examples/demo.c
index 7ccdb51.
Signed-off-by: Rafal Czubak <[EMAIL PROTECTED]>
Acked-by: Rafal Jaworowski <[EMAIL PROTECTED]>
---
api/api_storage.c | 16 +++-
1 files changed, 11 insertions(+), 5 deletions(-)
diff --git a/api/api_storage.c b/api/api_storage.c
index 7e63240..874c538 100644
--- a/api/api_storage.c
Signed-off-by: Rafal Czubak <[EMAIL PROTECTED]>
---
api_examples/demo.c | 17 +
1 files changed, 9 insertions(+), 8 deletions(-)
diff --git a/api_examples/demo.c b/api_examples/demo.c
index eae9712..7ccdb51 100644
--- a/api_examples/demo.c
+++ b/api_examples/demo.c
@@ -58,11 +58
On Jul 28, 2008, at 1:13 PM, Wolfgang Grandegger wrote:
> Kumar Gala wrote:
>> One topic that come up during OLS in discussions and u-boot BOF
>> was the idea of driving u-boot configuration from a device tree
>> instead of from "config.h". I was wondering if anyone has
>> actually looke
On Jul 28, 2008, at 12:40 PM, Grant Likely wrote:
> On Mon, Jul 28, 2008 at 10:07:49AM -0500, Kumar Gala wrote:
>> One topic that come up during OLS in discussions and u-boot BOF was
>> the idea of driving u-boot configuration from a device tree instead
>> of
>> from "config.h". I was wonderin
Hello Grant
Thanks for your comment. The use for the ddr2 is just an example...
I did developed it for that reason, but you can use it for anything
else. I sent the patch just because I thought it will be useful for
other people and the mail list response in that way. It was my first
patch to th
Kumar Gala wrote:
> One topic that come up during OLS in discussions and u-boot BOF was
> the idea of driving u-boot configuration from a device tree instead of
> from "config.h". I was wondering if anyone has actually looked at
> doing this.
Last year I brought up the topic twice:
http://
On Mon, Jul 28, 2008 at 10:43 AM, Scott Wood <[EMAIL PROTECTED]> wrote:
> Ben Warren wrote:
>>
>> On Mon, Jul 28, 2008 at 10:32 AM, Scott Wood <[EMAIL PROTECTED]>
>> wrote:
>>>
>>> I find a device tree much easier to figure out than a tangled mess of
>>> header
>>> files, #defines, and #ifdefs...
>
Heyello,
Doublee Your Sexual Pleasure
http://utr.cxuiskokeg.cn
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great
Ben Warren wrote:
> On Mon, Jul 28, 2008 at 10:32 AM, Scott Wood <[EMAIL PROTECTED]> wrote:
>> I find a device tree much easier to figure out than a tangled mess of header
>> files, #defines, and #ifdefs...
>
> In many ways, yes. But are you an average Joe or a Linux kernel
> propellerhead?
Is
On Mon, Jul 28, 2008 at 10:07:49AM -0500, Kumar Gala wrote:
> One topic that come up during OLS in discussions and u-boot BOF was
> the idea of driving u-boot configuration from a device tree instead of
> from "config.h". I was wondering if anyone has actually looked at
> doing this.
>
> On
> Do you try the patch that I send?
Sorry, yes I did try and this patch. It does allow the code to compile, but I
am having issues on the USB TX side (stdout). It appears that may be there are
still some architecture changes made somewhere in the ttyusb driver that are
not working with the OMAP
On Mon, Jul 28, 2008 at 10:32 AM, Scott Wood <[EMAIL PROTECTED]> wrote:
> Ben Warren wrote:
>>
>> On Mon, Jul 28, 2008 at 8:07 AM, Kumar Gala <[EMAIL PROTECTED]>
>> wrote:
>>>
>>> One topic that come up during OLS in discussions and u-boot BOF was
>>> the idea of driving u-boot configuration from a
Ben Warren wrote:
> On Mon, Jul 28, 2008 at 8:07 AM, Kumar Gala <[EMAIL PROTECTED]> wrote:
>> One topic that come up during OLS in discussions and u-boot BOF was
>> the idea of driving u-boot configuration from a device tree instead of
>> from "config.h". I was wondering if anyone has actually loo
On Mon, Jul 28, 2008 at 8:07 AM, Kumar Gala <[EMAIL PROTECTED]> wrote:
> One topic that come up during OLS in discussions and u-boot BOF was
> the idea of driving u-boot configuration from a device tree instead of
> from "config.h". I was wondering if anyone has actually looked at
> doing this.
>
Hi,
I have a freescale based MX27ADS development board. I am trying to port u-boot
to this board.
Is there a port thats already available? If not kindly suggest what could be
the nearest port to this board?
Thanks in advance.
TJ
Did you know? You can CHAT without downloading messenger
On Mon, Jul 28, 2008 at 12:06:21PM +0200, Ricardo Ribalda Delgado wrote:
> This driver provides access to a simulated i2c eeprom.
> This simulated eeprom could be very useful in boards with
> ddr2 memories and no i2c interfaces.
>
> Using this driver the user can simulate a spd eeprom
> of a ddr2
On Mon, Jul 28, 2008 at 9:29 AM, 이승열 <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I'm writing SMC9210 linux device driver. I cannot determine MAC
> address because there is no information.
> I want to get MAC address from U-boot. How to pass MAC address to linux
> kernel?
>
This depends greatly on your
Hi all,
I'm writing SMC9210 linux device driver. I cannot determine MAC address because
there is no information.
I want to get MAC address from U-boot. How to pass MAC address to linux kernel?
Please let me know how to exchange MAC address between U-boot and linux kernel.
Thank you in advance.
On 11:06 Mon 28 Jul , Hunter, Jon wrote:
> > I recall that this did work with release 1.1.6, so it could be interesting
> > to go back to 1.1.6 and see if it does work.
>
>
> Ok, so I did try with 1.1.6 and made the same changes to usbdcore_omap1510.c
> and usbtty does work fine. It would be
> I recall that this did work with release 1.1.6, so it could be interesting
> to go back to 1.1.6 and see if it does work.
Ok, so I did try with 1.1.6 and made the same changes to usbdcore_omap1510.c
and usbtty does work fine. It would be interesting to track-down where this
stopped working an
One topic that come up during OLS in discussions and u-boot BOF was
the idea of driving u-boot configuration from a device tree instead of
from "config.h". I was wondering if anyone has actually looked at
doing this.
One question I have is how does (or should) u-boot identify where to
fin
>> I tested the patches today, and looks like problem remained same, but I
>> am able to get it compiled without any errors.
>> I am able to detect OSK5912 as "low speed USB device using uhci_hcd". I
>> think it should get detected as full speed device.
>> but problem of getting every typed charact
Use CFG_MIPS_TIMER_FREQ when computing the baudrate divisor
on alchemy cpus.
Signed-off-by: Wolfgang Ocker <[EMAIL PROTECTED]>
---
diff --git a/cpu/mips/au1x00_serial.c b/cpu/mips/au1x00_serial.c
index 6309794..e8baab5 100644
--- a/cpu/mips/au1x00_serial.c
+++ b/cpu/mips/au1x00_serial.c
@@ -76,7 +
Hi Mark,
On Mon, Jul 28, 2008 at 3:16 AM, Mark Jackson <[EMAIL PROTECTED]> wrote:
> The MIMC200 board is based on Atmel's NGW100 dev kit,
> but with an extra 8MByte FLASH and 128KByte FRAM.
> ---
> diff --git a/board/atmel/mimc200/eth.c b/board/atmel/mimc200/eth.c
> new file mode 100644
> index
Hi,
I tested the patches today, and looks like problem remained same, but I am
able to get it compiled without any errors.
I am able to detect OSK5912 as "low speed USB device using uhci_hcd". I
think it should get detected as full speed device.
but problem of getting every typed character twice re
Le lundi 28 juillet 2008 à 12:59 +0200, Remy Bohmer a écrit :
> I am very certain that it worked on 1.1.5_atmel_1.4 version, with
> exactly the same USB memory stick as the one that does not work on
> thecurrent releases...
> So, I can rule the USB stick as well...
This makes you a good test conf
"Hong Xu" <[EMAIL PROTECTED]> wrote:
> The point is I'm not sure all AT91 series will behave the same way.
> But since AVR32 has less cases, it's a good idea to use #else to
> handle AT91 variants. So at least till now, this patch makes sense.
When I said "let's stop the overengineering", I meant
On Mon, Jul 28, 2008 at 17:24, Haavard Skinnemoen
<[EMAIL PROTECTED]> wrote:
> "Hong Xu" <[EMAIL PROTECTED]> wrote:
>> Per J's suggestion, use CONFIG_MACB_INCLK or some other thing to
>> simplify the *big* ifdef in driver/net/macb.c
>> From the existing code, it seems that some boards (AT91CAP9,
>
Hello Stelian,
> You're correct, USB support on the AT91SAM9 boards has some unknown
> issues. I can reproduce the behaviour you're seing easily here.
That is at least some good news. It confirms that I did not introduce
this problem myself :-)
> Nicolas Ferre (added in CC:) confirmed the proble
The MIMC200 board is based on Atmel's NGW100 dev kit,
but with an extra 8MByte FLASH and 128KByte FRAM.
RESENT to fix stupid line wrapping !! Sorry.
---
CREDITS|4 ++
MAINTAINERS|4 ++
MAKEALL|1 +
Makefile
The MIMC200 board is based on Atmel's NGW100 dev kit,
but with an extra 8MByte FLASH and 128KByte FRAM.
---
CREDITS|4 ++
MAINTAINERS|4 ++
MAKEALL|1 +
Makefile |3 +
board/atmel/mimc200/Make
This driver provides access to a simulated i2c eeprom.
This simulated eeprom could be very useful in boards with
ddr2 memories and no i2c interfaces.
Using this driver the user can simulate a spd eeprom
of a ddr2 memory and use the ddr2 auto config.
User can use the macros CONFIG_EEPROM_SIMUL_LEN
Le samedi 26 juillet 2008 à 00:22 +0200, Remy Bohmer a écrit :
> Hello Stelian,
Hi Rémy,
>
> Thank you for adding support for the Atmel AT91SAM9261-EK to U-boot.
>
> But I have a question here:
> Does USB-storage devices work in U-boot at your place? (e.g. 1GB USB
> memory stick)
> I use U-boot
"Hong Xu" <[EMAIL PROTECTED]> wrote:
> Per J's suggestion, use CONFIG_MACB_INCLK or some other thing to
> simplify the *big* ifdef in driver/net/macb.c
> From the existing code, it seems that some boards (AT91CAP9,
> AT91SAM926[0,3]) need the CLKEN bit of EMAC_USRIO to be set, but
> others(if exis
On Mon, Jul 28, 2008 at 16:29, Haavard Skinnemoen
<[EMAIL PROTECTED]> wrote:
> "Hong Xu" <[EMAIL PROTECTED]> wrote:
>> > maybe we can use config related to the functionnality or the sub-class
>> > CPU
>> > ex :
>> > CONFIG_MACB_INCLK
>>
>> Agree.
>>
>> We can use "#if defined(CONFIG_AT91) && define
"Hong Xu" <[EMAIL PROTECTED]> wrote:
> > maybe we can use config related to the functionnality or the sub-class
> > CPU
> > ex :
> > CONFIG_MACB_INCLK
>
> Agree.
>
> We can use "#if defined(CONFIG_AT91) && defined(CONFIG_MACB)" in
> net/eth.c and "#ifdef CONFIG_MACB_INCLK" in drivers/net/macb.c
Dear All,
I m newly using U-Boot in a customised platform of processor Intel xscale
PXA255.
U-Boot 1.1.6 (Jul 28 2008 - 10:01:53) is running in this board . In this
board one external 64 mb RAM is there and one 64 mb flash is there .
RAM address is starting from 0xA000 . Flash address is s
58 matches
Mail list logo
