This patch series contains a functional DNS323 configuration, and
other required changes. This is based on a point prior to the
relocation work.
This version is configured to be chained from the existing vendor
U-Boot, and is NOT intended to be flashed to NOR.
From: Rogan Dawes
Some SATA controllers can operate in an IDE compatible mode (e.g. mvsata)
but will only ever have a single device per bus.
This allows the upcoming DNS323 port to properly identify and use
a drive on both SATA interfaces.
---
include/ide.h |3 ++-
1 files changed, 2
From: Albert Aribaud
Commit 64419e47518bbba059c80b77558f93ad4804145c aliases
the uint16_t usp and uint32_t uip variables in print_buffer()
to uint8_t variable linebuf without aligning it to an uint32_t
address, thus causing data aborts on ARM when doing md.l on
32-bit wide area (and probably 16-
From: Albert Aribaud
Fix orion5x_winctrl_calcsize() off-by-1 bug which caused mapping
windows to be cut by half. This afected all windows including NOR
flash (causing half the flash to be unaccessible) but DRAM was and
still is fine as its size is determined otherwise.
Signed-off-by: Albert Arib
From: Albert Aribaud
This driver is for the Marvell TWSI/I2C module found in
the orion and kirkwood families among others.
Signed-off-by: Albert Aribaud
---
drivers/i2c/Makefile |1 +
drivers/i2c/mvtwsi.c | 419 ++
2 files changed, 420 inser
From: Albert Aribaud
Signed-off-by: Albert Aribaud
---
include/configs/edminiv2.h |9 +
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/include/configs/edminiv2.h b/include/configs/edminiv2.h
index 57dd165..36ed392 100644
--- a/include/configs/edminiv2.h
+++ b/include
From: ro...@dawes.za.net
This allows us to match the exact behaviour of the vendor U-boot in the kernel
boot logs
---
arch/arm/cpu/arm926ejs/orion5x/dram.c |2 +-
common/memsize.c |3 +++
2 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/arch/arm/cpu/ar
From: Rogan Dawes
---
arch/arm/cpu/arm926ejs/orion5x/dram.c |2 +-
arch/arm/include/asm/arch-orion5x/orion5x.h |1 +
2 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/arch/arm/cpu/arm926ejs/orion5x/dram.c
b/arch/arm/cpu/arm926ejs/orion5x/dram.c
index c719798..90b0a9c
From: Rogan Dawes
---
drivers/mtd/cfi_flash.c | 22 +-
1 files changed, 21 insertions(+), 1 deletions(-)
diff --git a/drivers/mtd/cfi_flash.c b/drivers/mtd/cfi_flash.c
index 44ebb9d..7ee4f90 100644
--- a/drivers/mtd/cfi_flash.c
+++ b/drivers/mtd/cfi_flash.c
@@ -262,6
From: Rogan Dawes
---
arch/arm/include/asm/setup.h | 18 ++
arch/arm/lib/bootm.c | 30 ++
2 files changed, 48 insertions(+), 0 deletions(-)
diff --git a/arch/arm/include/asm/setup.h b/arch/arm/include/asm/setup.h
index 89df4dc..bd6229a
From: ro...@dawes.za.net
---
common/image.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/common/image.c b/common/image.c
index fcb938b..eea93a9 100644
--- a/common/image.c
+++ b/common/image.c
@@ -949,7 +949,7 @@ int boot_get_ramdisk (int argc, char * const argv[],
I may be doing wrong are gratefully
received.
Regards,
Rogan
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
From: Rogan Dawes
---
arch/arm/cpu/arm926ejs/orion5x/dram.c |2 +-
arch/arm/include/asm/arch-orion5x/orion5x.h |1 +
2 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/arch/arm/cpu/arm926ejs/orion5x/dram.c
b/arch/arm/cpu/arm926ejs/orion5x/dram.c
index b749282..2ae8f48
From: Rogan Dawes
Some SATA controllers can operate in an IDE compatible mode (e.g. mvsata)
but will only ever have a single device per bus.
This allows the upcoming DNS323 port to properly identify and use
a drive on both SATA interfaces.
---
include/ide.h |3 ++-
1 files changed, 2
From: Rogan Dawes
This allows us to match the exact behaviour of the vendor U-boot in the kernel
boot logs
---
arch/arm/cpu/arm926ejs/orion5x/dram.c |2 +-
common/memsize.c |3 +++
2 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/arch/arm/cpu
From: Rogan Dawes
---
drivers/mtd/cfi_flash.c | 22 +-
1 files changed, 21 insertions(+), 1 deletions(-)
diff --git a/drivers/mtd/cfi_flash.c b/drivers/mtd/cfi_flash.c
index dd394a8..74e9ade 100644
--- a/drivers/mtd/cfi_flash.c
+++ b/drivers/mtd/cfi_flash.c
@@ -291,6
From: Rogan Dawes
---
arch/arm/include/asm/setup.h | 18 ++
arch/arm/lib/bootm.c | 31 +++
2 files changed, 49 insertions(+), 0 deletions(-)
diff --git a/arch/arm/include/asm/setup.h b/arch/arm/include/asm/setup.h
index 89df4dc..bd6229a
From: Rogan Dawes
---
common/image.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/common/image.c b/common/image.c
index f63a2ff..108bb44 100644
--- a/common/image.c
+++ b/common/image.c
@@ -950,7 +950,7 @@ int boot_get_ramdisk (int argc, char * const argv
From: Rogan Dawes
Based on that of the edminiv2, with a few additions
The image is configured to boot vendor kernels seamlessly.
i.e. the kernel boot logs should be identical between the vendor
bootloader and this mainline version.
Note that the vendor flash layout does not allow space for
From: Rogan Dawes
Based on that of the edminiv2, with a few additions
The image is configured to boot vendor kernels seamlessly.
i.e. the kernel boot logs should be identical between the vendor
bootloader and this mainline version.
Note that the vendor flash layout does not allow space for
ion that anything was running.
Any other suggestions?
Regards,
Rogan
On Tue, 22 Aug 2023 at 04:33, Fabio Estevam wrote:
>
> Hi Rogan,
>
> On Fri, Aug 18, 2023 at 10:45 AM Rogan Dawes wrote:
> >
> > Circling back to this, I wanted to get a modern u-boot running on the
>
Hi Fabio,
On Tue, 22 Aug 2023 at 13:44, Fabio Estevam wrote:
>
> Hi Rogan,
>
> On Tue, Aug 22, 2023 at 6:42 AM Rogan Dawes wrote:
> >
> > Hi Fabio,
> >
> > As far as I am aware, the U-boot source for the Wink hub has not been
> > made available anywh
e pins. i was hoping to see it
boot via mxsldr, but unfortunately, I got nothing.
How can I get the SPL to emit something on the console to confirm it is
running? i.e. before the DRAM initialisation?
Regards,
Rogan
On Wed, 23 Aug 2023 at 17:56, Rogan Dawes wrote:
> Hi Fabio,
>
>
= <
@@ -404,6 +415,20 @@
fsl,pull-up = ;
};
+ auart4_pins_a: auart4-4pins@0 {
+ reg = <0>;
+ fsl,pinmux-ids = <
+ MX28_PAD_SAIF0_BITCLK__AUART4_RX
+ MX28_PAD_SAIF0_SDATA0__AUART4_TX
+ MX28_PAD_SAIF0_MCLK__AUART4_CTS
+ MX28_PAD_SAIF0_LRCLK__AUART4_RTS
+ >;
+ fsl,drive-strength
Hi Fabio,
On Mon, 25 Sep 2023 at 15:04, Fabio Estevam wrote:
> Hi Rogan,
>
> On Mon, Sep 25, 2023 at 6:52 AM Rogan Dawes wrote:
> >
> > Hi Fabio,
> >
> > I used the following diff with "make mx28evk_defconfig", but
> unfortunately still ge
sly.
With CONFIG_SPL_MXS_PMU_MINIMAL_VDD5V_CURRENT=y AND
CONFIG_SPL_MXS_PMU_DISABLE_BATT_CHARGE=y, I get LLC\nPref
With all three =y, I just get L
Rogan
On Mon, 25 Sept 2023 at 17:50, Fabio Estevam wrote:
>
> On Mon, Sep 25, 2023 at 11:00 AM Rogan Dawes wrote:
>
> > I see absolutely nothing in the console.
> &
Hi Fabio,
That prints "LLC", but does not print "Pref".
Rogan
On Tue, 26 Sept 2023 at 02:15, Fabio Estevam wrote:
> Hi Rogan,
>
> On Mon, Sep 25, 2023 at 4:27 PM Rogan Dawes wrote:
> >
> > That outputs LLC about a second after the mxsldr terminates (
0.
Where are the LLC characters coming from? It's a little tricky to grep the
source for a single character :-(
Rogan
On Tue, 26 Sept 2023 at 18:47, Fabio Estevam wrote:
>
> Hi Rogan,
>
> On Tue, Sep 26, 2023 at 1:01 AM Rogan Dawes wrote:
> >
> > Hi Fabio,
>
t I suspect that I may not have made the updates
sufficiently well, if the name of the board needs to correspond with
any details of the device tree? Neither of these resulted in any
output.
Any other suggestions?
Regards,
Rogan Dawes
On Fri, 23 Jun 2023 at 03:25, Fabio Estevam wrote:
>
>
ipermail/u-boot/2010-August/075589.html
I seem to recall Wolfgang was not terribly enthused about it for some
reason, though.
Rogan
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
e of the partition */
> + u32 offset; /* offset within device */
> + void *jffs2_priv; /* used internaly by jffs2 */
Should this really be in here? Seems we are mixing things up still.
> /* XXX U-BOOT XXX */
> #if 0
> struct mtd_notifier {
ltiple places?
Does that make any more sense? Is it possible that the CFI code in
U-Boot doesn't consider the case when bus_width == 2?
Regards,
Rogan
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
at was an issue long ago, I made the board/emk/common/flash.c
> (CFI) driver. Anyone is welcome to add that special handling for 16 bit
> flash connected in 8 bit mode to the general CFI driver :)
Thanks a lot! I'll take a look, and see if I can understand it. :-)
Rogan
lude/configs/openrd_base.h:#define CONFIG_MVSATA_IDE_USE_PORT1
$
i.e. CONFIG_MVSATA_IDE_USE_PORT1 is defined, but never used for anything.
Regards,
Rogan
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
ype
1 63 1060227 82
2 2088450 -1366783681 83
4 1060290 1028160 83
I'm not sure how or where to fix this, though.
Rogan
___
U-Boot mailing list
U-Boot@lists.denx
On 2010/08/13 2:57 PM, Vitaly Kuzmichev wrote:
> Replace Linux-like debug printout macros by native ones.
>
> Signed-off-by: Vitaly Kuzmichev
> ---
> drivers/usb/gadget/ether.c | 99
> ---
> 1 files changed, 46 insertions(+), 53 deletions(-)
>
> diff --
need to touch
general code when trying to debug my board.
I can just define that in my board config. Although, that could lead to
a proliferation of *_DEBUG defines, which may or may not be documented.
Perhaps without the CONFIG_ part, and people who are trying to debug
their boards need to re
On 2010/08/14 10:14 AM, Albert ARIBAUD wrote:
> Rogan, please test it and see if it fixes your issue as well (can't
> swear that it will).
>
> Mike, please test it and see if it does not regress on your side (can't
> see why it should, but maybe the __aligned__ attribute
E(dev)
(CONFIG_SYS_ATA_BASE_ADDR+ide_bus_offset[IDE_BUS(dev)])
Ok, I'm sure it is line wrapped, tab-damaged, etc, and the line itself
is too long, but conceptually, would that be acceptable?
Thanks
Rogan
___
U-Boot mailing list
U-Boot@lists.denx.de
h
On 2010/08/14 12:41 PM, Rogan Dawes wrote:
> -#defineIDE_BUS(dev)(dev>> 1)
> +#defineIDE_BUS(dev)(dev>> (CONFIG_SYS_IDE_MAXDEVICE /
> CONFIG_SYS_IDE_MAXBUS - 1))
>
>#defineATA_CURR_BASE(dev)
> (CONFIG_SYS_ATA_BASE_ADDR+ide_bus_off
Some SATA controllers can operate in an IDE compatible mode (e.g. mvsata)
but will only ever have a single device per bus.
This allows the upcoming DNS323 port to properly identify and use
a drive on both SATA interfaces.
---
include/ide.h |3 ++-
1 files changed, 2 insertions(+), 1 deletions
This addresses Wolfgang's suggestion to use additional parens
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
From: Rogan Dawes
Some SATA controllers can operate in an IDE compatible mode (e.g. mvsata)
but will only ever have a single device per bus.
This allows the upcoming DNS323 port to properly identify and use
a drive on both SATA interfaces.
---
include/ide.h |3 ++-
1 files changed, 2
to load at 0x300,
and stay there (no relocation), if I have understood these parameters
correctly:
-a 0x300 -e 0x300
Can anyone see what I am doing wrong?
Many thanks!
Rogan
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
On 2010/08/16 10:34 AM, Gérald Kerma wrote:
> Dear Rogan,
>
> I've you set the uboot env machid to the correct value ?
> setenv machid
> just replace HexValue with the correct MACH_TYPE.
>
> You must then see something like :
> Using machid 0xa76 from environment
&
On 2010/08/16 9:24 AM, Rogan Dawes wrote:
> Hi folks,
>
> I'm trying to get mainline u-boot working on my DNS323 (Orion5x based).
> Until I am confident in the config, I'm using a chainloaded approach,
> wrapping my featureful u-boot in an image file:
>
> $ mkimag
On 2010/08/16 10:29 PM, Wolfgang Denk wrote:
> Dear Rogan Dawes,
>
> In message<4c699c6e.2010...@dawes.za.net> you wrote:
>>
>>> DNS323B1> bootm FF82
>>> ## Booting kernel from Legacy Image at ff82 ...
>>> Image Name: Linux-2.6
From: Rogan Dawes
---
arch/arm/include/asm/arch-orion5x/cpu.h |2 +-
board/D-Link/dns323_b1/Makefile | 53 +
board/D-Link/dns323_b1/config.mk| 27 +++
board/D-Link/dns323_b1/dns323_b1.c | 129 +++
board/D-Link/dns323_b1
On 2010/08/17 12:03 AM, Wolfgang Denk wrote:
> Dear Rogan Dawes,
>
> In message <4c69a8da.8020...@dawes.za.net> you wrote:
>>
>>> Are you absolutely sure that you have RAM in your system at 0x8000?
>>> I doubt that your Load Address/Entry Point settings
On 2010/08/17 12:10 PM, Albert ARIBAUD wrote:
> (quick note to Wolfgang: yes, there is RAM at 0x8000 on these
> machines. All orion5x based machines have RAM start at 0, and u-boot
> makes sure SDRAM is set up this way)
>
> Rogan,
>
> You cannot tell from your log outp
rwritten by Linux (unless I load a
> 63+ MB kernel, that is :) )
That was my reasoning with the 48MB, too :-)
Rogan
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
On 2010/08/17 1:19 PM, Rogan Dawes wrote:
> I'll try with a higher value, and see what happens.
>
So, I tried with TEXT_BASE=f1, and I got a bit further:
DNS323B1> bootm FF82
## Booting kernel from Legacy Image at ff82 ...
Image Name: Linux-2.6.12.6-arm1
Ima
efine MACH_TYPE_DNS323 526
Making the above change results in a booting kernel, until the root fs
can not be found.
Am I mistaken in expecting the machid environment variable trick to work?
Thanks
Rogan
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
On 2010/08/17 9:56 PM, Rogan Dawes wrote:
>
> Am I mistaken in expecting the machid environment variable trick to work?
>
> Thanks
>
> Rogan
No, but mistaken in thinking that the machid was in decimal, when it is
really in hex.
Now to figure out why the CRC calculations
On 2010/08/17 11:20 PM, Wolfgang Denk wrote:
> Dear Rogan Dawes,
>
> In message <4c6aec70.40...@dawes.za.net> you wrote:
>>
>> No, but mistaken in thinking that the machid was in decimal, when it is
>> really in hex.
>>
>> Now to figure out why the
On 2010/08/18 12:04 AM, Wolfgang Denk wrote:
> Dear Rogan Dawes,
>
> In message <4c6b051a.5050...@dawes.za.net> you wrote:
>>
>> For some reason, the kernel didn't seem to think it had been given the
>> ramdisk parameter. At least, I get the following er
On 2010/08/18 7:51 AM, Wolfgang Denk wrote:
> Dear Rogan Dawes,
>
> In message <4c6b08f1.9000...@dawes.za.net> you wrote:
>>
>> The ramdisk is located at ff9a (in flash). Its image header
>> relocates it to 0080:
>
> Try to copy the ramdisk to RAM,
On 2010/08/18 12:54 PM, Wolfgang Denk wrote:
> Dear Rogan Dawes,
>
> In message <4c6bac5a.6060...@dawes.za.net> you wrote:
>>
>> Thanks for the suggestion. It did make a slight difference in the boot
>> logs. bootcmd uses the default (in flash) location for
On 2010/08/18 5:33 PM, Wolfgang Denk wrote:
> Dear Rogan Dawes,
>
> Your kernel may not be able to pick up a ramdisk image in flash.
>
> Mainline ARM cannot do that, for example.
>
> [Patches to support that have been submitted, but rejected.]
>
>> Surely that sh
in
the hope of getting suggestions on how to improve it.
I didn't see much point in a SoB until it was ready to be submitted for
real.
Thanks for taking a look at it, though.
Rogan
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.d
On 2010/08/19 7:35 AM, Wolfgang Denk wrote:
> Dear Rogan Dawes,
>
> In message <4c6cc059.4080...@dawes.za.net> you wrote:
>>
>> The patch was simply to allow people to see my non-working config, in
>> the hope of getting suggestions on how to improve it.
>
ame in
your terminal software, and you should be able to continue. Press Enter
a couple of times to get your prompt back.
While it will be slower than 115200, it will likely be better than
introducing artificial delays after each character.
Rogan
_
t:
>
> setenv enaPost Yes
>
> setenv enaCpuStream Yes
>
> and saved them:
>
> saveenv
>
It sounds like you may have to investigate a JTAG cable. Try opening it
up, and seeing if you can find a 12 or 14 pin header. It *MAY* be a jtag
header.
Google for more i
of the boot sequence.
Take a look at cmd_bootm.c.
It may be platform dependent, though. What architecture are you working
with?
Rogan
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
eal reason for the change.
Rogan
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
On 2010/08/24 8:07 AM, Albert ARIBAUD wrote:
> Le 24/08/2010 07:21, Chris Moore a écrit :
>> Hi Rogan,
>>
>> Le 23/08/2010 18:06, Rogan Dawes a écrit :
>>> Doubling the value for ORION5X_SZ_BOOTROM allowed me to access the
>>> additional sectors, but that ma
On 2010/08/24 1:34 PM, Albert ARIBAUD wrote:
> Le 24/08/2010 09:47, Rogan Dawes a écrit :
>
>> Yes, I still have the vendor u-boot flashed, so I can still see its
>> configuration. And, yes, it does allow reading the full 8MB of flash.
>
>> Vendor u-boot:
>
This code was referencing the wrong register, and only
happened to "work" because the DRAM on both users of this
code happened to be a single bank located at address 0.
Signed-off-by: Rogan Dawes
---
Prafulla, according to Albert, this code was copied from
the Kirkwood code,
On 2010/08/16 7:47 AM, Rogan Dawes wrote:
> From: Rogan Dawes
>
> Some SATA controllers can operate in an IDE compatible mode (e.g. mvsata)
> but will only ever have a single device per bus.
>
> This allows the upcoming DNS323 port to properly identify and use
> a drive on
mean we only need board.cfg change and we don't need Makefile
> entry ?
Yes, exactly.
Rogan
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
On 2010/09/04 11:07 AM, Albert ARIBAUD wrote:
> Le 04/09/2010 10:22, Albert ARIBAUD a écrit :
>> Le 26/08/2010 15:16, Rogan Dawes a écrit :
>>
>>> Anything wrong with this patch?
>>
>> I think I finally found what was bugging me with it.
>>
>>
ns from the code.
FWIW.
Rogan
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
it that will.
>
> Amicalement,
You should probably take a closer look at the patch itself. It seems to
be changing lines that you do not intend to, such as the copyright lines
(I guess it is an encoding issue).
Rogan
___
U-Boot mailing list
U-Bo
eers,
> Stefan
Hi Stefan,
Have you had any thoughts about what the CONFIG_CFI option should be
called for the odd flash arrangement on my DNS323? If you let me know
what to call it, I'll submit a patch.
Thanks
Rogan
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
On 2010/09/16 5:10 PM, Stefan Roese wrote:
> Hi Rogan,
>
> On Thursday 16 September 2010 16:21:05 Rogan Dawes wrote:
>> Have you had any thoughts about what the CONFIG_CFI option should be
>> called for the odd flash arrangement on my DNS323? If you let me know
>> wha
used as it is
introduced, rather than building up a whole lot of unused
infrastructure, only to activate it with a final commit. The bisection
would then point to the final commit as the culprit, when the true
failure may have been introduced by one of the preceding commits.
That's "as I un
On 2010/09/24 6:45 PM, Rogan Dawes wrote:
> On 2010/09/24 7:47 AM, Albert ARIBAUD wrote:
>
>> On a side note, I do not know of a clear general definition of
>> 'bisectability', which means I could break it yet again unkonwingly. Can
>> you (or anyone, actual
On 2010/09/29 11:29 AM, Wolfgang Denk wrote:
> +Why: The implementation of U-Boot for the ARM architecture has
> + been reworked to support relocation. This allows to
> + efficiently use the same U-Bot binary image on systems with
U-Bo
0_BASEKW_UART0_BASE
> +#define MV_UART0_BASEKW_UART0_BASE
dup?
> +/*
> + * IDe Support on SATA port0
> + */
IDe?
Rogan
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
On 2010/09/30 4:33 PM, Prafulla Wadaskar wrote:
>>> +/*
>>> + * IDe Support on SATA port0
>>> + */
>>
>> IDe?
>
> I think Ide can be removed, right?
I was just commenting on the (mis-)capitalisation.
Rogan
___
t does not work, however -- ping or tftp just wait without me
> being able to ^C it. I'll look into that as soon as some domestic chores
> are done. :)
Excellent work! Congratulations!
Rogan
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
ot; for "SDRAM" got me nowhere.
Surely having e.g.
#if (not fixed config)
#error See http://blah/blah/blah for information about how to fix your board
#endif
would be more beneficial than an obscure compiler failure that doesn't
even reference useful keywords?
Regards,
ndations I
> really would aprecciate it.
>
> Thank you all.
> Best Regard,.
>
> Gustavo Silva
I have no skills at all, but I'd also be interested in a port to
Stellaris processors, since I just ordered one of the TI EvalBot's:
http://hackaday.com/2010/10/04/125-of
es not handle
> long (multiline) strings nicely...
>
> Best Regards,
> Reinhard
Keep in mind that the Linux folk are looking for an alternative to the
defconfig mess that they have currently.
Linus has stated that he will delete all the ARM defconfigs soon.
Rogan
__
On 2010/10/07 7:22 AM, Wolfgang Denk wrote:
> Dear Rogan Dawes,
>
> In message <4cad569e.3020...@dawes.za.net> you wrote:
>>
>> Keep in mind that the Linux folk are looking for an alternative to the
>> defconfig mess that they have currently.
>>
>> Lin
t actually references that value to
place the start code at that point.
I'm basically trying to make sure that my CONFIG_SYS_TEXT_BASE is
correct (the address in the flash to which I write the whole u-boot.bin
file, right?.
Thanks
Rogan
___
U-Boot mail
On 2011/04/20 7:42 AM, Albert ARIBAUD wrote:
> Le 20/04/2011 04:23, Hebbar, Gururaja a écrit :
>> Hi,
>>
>> On Wed, Apr 20, 2011 at 02:43:23, Rogan Dawes wrote:
>>> Hi folks,
>>>
>>> I'm trying to understand a bit more about how u-boot cre
On 2011/04/20 10:29 AM, Albert ARIBAUD wrote:
> Hi Rogan,
>
> Le 20/04/2011 09:46, Rogan Dawes a écrit :
>> On 2011/04/20 7:42 AM, Albert ARIBAUD wrote:
>>> Le 20/04/2011 04:23, Hebbar, Gururaja a écrit :
>>>> Hi,
>>>>
>>>> On Wed,
On 2011/04/20 12:17 PM, Rogan Dawes wrote:
> Now if I can just figure out how to write to my flash using OpenOCD, I
> can hopefully recover.
>
> Regards,
>
> Rogan
Phew! Thanks to Albert's sloflash utility, I was finally able to get
something back into my flash, and get
ll your help while I learned about U-Boot, JTAG, debugging,
contributing, etc.
Regards,
Rogan
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
0054 in ?? ()
(arm-gdb)stepi
Program received signal SIGINT, Interrupt.
0x0358 in ?? ()
(arm-gdb)symbol-file u-boot-standalone-0x300
Reading symbols from
/home/rogan/openocd/u-boot-standalone-0x300...BFD:
/home/rogan/openocd/u-boot-standalone-0x300: invalid string offset
37 >= 0 for se
simply posted the patch as part of my DNS323 series. However, Prafulla
saw it and merged it some time ago.
Regards,
Rogan
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
I wrote 3 weeks ago, with no response:
> Hi folks,
>
> I have an ADSL router (Linksys WAG200G) that is based on the TI AR7
> (MIPS) architecture.
>
[snip]
> So, does Das U-Boot support the AR7 family of chips? The CPU is labeled
> TNETD7300GDU (52A29HW), if that helps.
&g
icult is it to port such things from Linux to U-Boot? Is it as
simple as copying files from the Linux sources, and a little glue to
enable linking them in (similar to how the UBIFS stuff has been
introduced), or is it a lot more complex than that?
Thanks
iling with 4.5 results
in a non-working image. If anyone wants to work out what the differences
are, and how to get 4.5 to build successfully, please let me know.
Regards,
Rogan
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listi
h set for the DNS323, for what it is
worth. I must have needed it, but I can't remember exactly what the
behaviour was without it. :-)
Rogan
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
at the CFI code works fine with the flash hooked up as 16-bit on a 16-
> bit bus.
>
> If it's an 8-bit flash on a 16-bit bus then the addresses should be doubled.
>
>
> -Aaron
Hi Aaron,
Does this patch (originally by Stefan Roese) work for you? I also need
it for th
ion of the posting. My
cover letter stated that it was a functional port of U-Boot to the
DNS323, based on a (VERY) old starting point, prior to the relocation
work. I was posting it to show that I DO have a working port for the
DNS323, and to contrast that with the non-working post-relocation
On 2011/03/18 11:22 AM, Heiko Schocher wrote:
> Hello Rogan,
>
> Rogan Dawes wrote:
>> On 2011/03/18 10:29 AM, Heiko Schocher wrote:
>>> Hello ro...@dawes.za.net,
>>>
>>
>>> This patch could not be against current head! There is no
>>>
fine CONFIG_CMD_I2C
>
> Pls defind _CMD_I2C above with other enabled commands and #ifdefed this stuff
> in it.
>
> Regards..
> Prafulla . .
Hi Prafulla,
I only posted this series to have a record of a working config in the
archives. This patch is against 2010.06-something,
1 - 100 of 143 matches
Mail list logo