Hi,
Sorry for that.
Now i have generated the patch using below command. Update me if this is not
correct
$ git format-patch -p -o ../ -C -M -N --summary --stat=80 --no-color
--signoff master workingbranch
TIA
Regards
Gururaja
- Add ARM AMBA PL031 RTC Support
- Call rtc_init function to s
> Yes, you're right. it's complicit.
> However it's not related with this patch. It happens always at current
> source.
> Next time it will fix it.
>
The kernel implementation is similar. You'll probably have to fix it there
also.
cheers,
Fathi
---
Hi,
2008/7/19 Rodrigo Valentino <[EMAIL PROTECTED]>:
> Hi Folks,
>
> I'm working on a device from ST Micro Eletronics model ST7100, and i'm
> looking for a way to improve redirect output console to device ttyUSB,
> because the serial output
>
I suppose that you use U-Boot which STMicro releases.
In message <[EMAIL PROTECTED]> you wrote:
>
> I think nabble wont truncate or line wrap my mail. So i am giving it a try.
Don't think - test before sending to public mailing lists.
...
> +#define RTC_WRITE_REG(addr, val)(*(volatile unsigned int
> *)(CFG_RTC_PL031_BASE + (addr)) = (
They only differ in the init function.
This also adds the missing watchdog support for the PL011.
Signed-off-by: Andreas Engel <[EMAIL PROTECTED]>
---
Added to GNATS database as unassigned-patches/3
>Responsible:patch-coord
>Message-Id: <[EMAIL PROTECTED]>
>In-Reply-To:
>References:
On Fri, Jul 18, 2008 at 11:09 PM, Fathi Boudra <[EMAIL PROTECTED]> wrote:
> Hi,
>
>> > > I really would rather not duplicate all of this, which looks extremely
>> > > similar to regular NAND. Is there reason why we don't use the
>> > > mtd_info
>> > > function pointer interface?
>> >
>> > Agreed,
Hi,
I think nabble wont truncate or line wrap my mail. So i am giving it a try.
I have added changes required for versatile board to call rtc_init &
defines in include/configs/versatile.h to include pl031 rtc definitions
Kindly comment
TIA
Regards
Gururaja
- Add ARM AMBA PL031 RTC Support
Hi folks,
I use Atmel AT91SAM9260-EK boards, arm-linux-gcc (GCC) 4.2.4. After I
pulled the latest code from git://git.denx.de/u-boot-at91.git, I found
that the [EMAIL PROTECTED]/env_common.c can not work well. The root
cause is in u-boot-1.3.4-rc1, `env_get_char' was rewritten. Below is a
quick pat
Hi j,
>> Could you please send your patch as inline, otherwise it's really
difficult to comment use git-send-email as example
>> and also please read this http://www.denx.de/wiki/UBoot/Patches
>> and http://lwn.net/Articles/139918/
Sorry for the whitespace mistakes. i have now corrected it.
B
Claudio,
In the data sheet I can not find a reference to on oobsize of 512, But
I do find the 0x2E on page
24 under byte 3 description. It brakes down to;
page size => 4K
Spare area size (bytes) => 218
Block size => 256KB
Organization => x8
Serial access (MIN) => 20ns
I did find a reference to t
This patch adds support for Beagle Board.
Beagle board from TI is a development platform
based on TI's OMAP3530 silicon.
You can find more about Beagle Board here: www.beagleboard.org
More on OMAP3530 (including documentation can be found here):
http://focus.ti.com/docs/prod/folders/print/omap353
Remove duplicate OMAP3_CLOCK_CONFIG introduced by
commit ID 5e4390fe
Signed-off-by: Raghavendra KH <[EMAIL PROTECTED]>
---
arch/arm/mach-omap/Kconfig |6 --
1 file changed, 6 deletions(-)
Index: u-boot-v2/arch/arm/mach-omap/Kconfig
===
Introduce a common board header for functions
required by platform.S This will prevent
redundancies of multiple board-xyz.h files all
doing the same thing.
This deletes the redundant board-sdp343x.h and
fixes the corresponding .c for the change.
Signed-off-by: Raghavendra KH <[EMAIL PROTECTED]>
There's no I2C devices.
Signed-off-by: Kyungmin Park <[EMAIL PROTECTED]>
---
diff --git a/include/configs/apollon.h b/include/configs/apollon.h
index 8973296..5884611 100644
--- a/include/configs/apollon.h
+++ b/include/configs/apollon.h
@@ -103,14 +103,6 @@
*/
#defineCONFIG_SERIAL1 1
Thanks Claudio for the information,
I've taken a look at the data sheet and it does not fit the typical
large page flash, but It does not mean its not supported under Linux
which is were the FLASH subsystem in U-Boot comes from. Neither am I
familiar with the open nand flash interface onfi.org. BU
In message <[EMAIL PROTECTED]> you wrote:
>
> I guess in some cases a board with fixed DDR would not
> need to initialize the I2C controller until after
> relocation.
If ever - let's keep in mind that U-Boot initializes only devices
which it actually uses itself.
Best regards,
Wolfgang Denk
--
In message <[EMAIL PROTECTED]> you wrote:
>
> > + if (gd->flags & GD_FLG_RELOC)
> Maybe a macro will more clear like
> if(is_relacated())
Actually, I disagree here.
Also, for consistency you would have to change many other uses of
(gd->flags & GD_FLG_???) as well.
Let's keep as is.
Best
Timur Tabi wrote:
> David Hawkins wrote:
>> Hi Timur,
[snip]
>> If you need I2C speed tracking code, why not just re-read
>> the I2C controller registers, and determine the speed from
>> there? That is independent of relocation.
>
> I suppose we could do that.
That won't work for soft (bit-bang
David Hawkins wrote:
> Hi Timur,
>
>> -i2c_bus_speed[0] = set_i2c_bus_speed(dev, gd->i2c1_clk, speed);
>> +temp = set_i2c_bus_speed(dev, gd->i2c1_clk, speed);
>> +if (gd->flags & GD_FLG_RELOC)
>> +i2c_bus_speed[0] = temp;
>
> Does i2c_init() get called again after relocati
> +/* Enable RTC Start in Control register*/
> +void rtc_init(void)
> +{
> + RTC_WRITE_REG(RTC_CR,RTC_CR_MIE);
please replace by
RTC_WRITE_REG(RTC_CR, RTC_CR_MIE);
> +
^
please remove this whitescpace
> + pl031_initted = 1;
> +}
> +
> +/*
> + * Reset the RTC. We set the
Hi Timur,
> - i2c_bus_speed[0] = set_i2c_bus_speed(dev, gd->i2c1_clk, speed);
> + temp = set_i2c_bus_speed(dev, gd->i2c1_clk, speed);
> + if (gd->flags & GD_FLG_RELOC)
> + i2c_bus_speed[0] = temp;
Does i2c_init() get called again after relocation?
If the I2C code is only
On 13:34 Mon 21 Jul , Gururaja Hebbar K R wrote:
> Hi,
>
> > >> Are you going to add a board which will use it?
> > >> Right now i am using it on arm Versatile board. Should i send a
> patch
> > >> to that also
>
> > >>If you do I can test it
>
> > >>Regards
> > >>Peter
>
Could you pleas
Jean-Christophe PLAGNIOL-VILLARD wrote:
> Maybe a macro will more clear like
> if(is_relacated())
> i2c_bus_speed[0] = temp;
I'm just following the same pattern as other code. The code "if (gd->flags &
GD_FLG_RELOC)" is used in a number of other places.
Someone else can crea
In message <[EMAIL PROTECTED]> you wrote:
>
> > And of course even 00:11:22:33:44:55 is not a legal MAC address and
> > MUST NOT BE USED. Please see the FAQ.
>
> Actually, 00:11:22:33:44:55 is a perfectly legal (universally
> administered) MAC address:
You are of course right - I was too terse.
On 14:26 Mon 21 Jul , Timur Tabi wrote:
> Prevent i2c_init() in fsl_i2c.c from writing to the data segment before
> relocation. Commit d8c82db4 added the ability for i2c_init() to program the
> I2C bus speed and save the value in i2c_bus_speed[], which is a global
> variable. It is an error t
Claudio,
This does not appear to be a standard large page device witch has;
page size of 2048 bytes plus 64 bytes OOB
block size of 129KiB plus 4096 OOB
Do you have the data sheet or are you determining the information
below from the ID byte?
Stuart
http://www.linux-mtd.infradead.org/doc/nand
> Ken Fuchs wrote:
> > There are at least two problems with your U-Boot 1.1.3
> > configuration:
> > vijays vijays wrote:
> > > #define CONFIG_ETHADDROO:11:22:33:44:55
> > > /* board MAC addr */
> > The first byte "OO" is two capital Os; perhaps "00" was the intended
> > first byte
Hi Nathan,
--- On Mon, 7/21/08, Nathan Manning <[EMAIL PROTECTED]> wrote:
> I noticed that the litektit's config.mk file has a
> TEXT_BASE of 0x87f0
> which doesn't correspond to our board's flash
> range. Is this really where
> u-boot should be loaded?
0x87F is an address in RAM, not fla
Stuart,
It is as follows:
The fourth byte is 0x2E which breaks down as follows:
oobsize = 512
oobblock = 4096
erasesize = 256k
busw = 8
Additional info:
1 page = 4k + 218 bytes
1 block = (4k +218 bytes) x 64 pages = (256k +13k) bytes
Device total size = 8,608Mbit
Thanks
Claudio
-Origi
Prevent i2c_init() in fsl_i2c.c from writing to the data segment before
relocation. Commit d8c82db4 added the ability for i2c_init() to program the
I2C bus speed and save the value in i2c_bus_speed[], which is a global
variable. It is an error to write to the data segment before relocation,
which
Hi Jerry,
> One really good trick is how to hook a logic analyzer to those
> itty-bitty balls on the processor. Back when I was a boy, processors
> had 40 legs and no balls. :-D You must have a board with a logic
> analyzer connector.
Thankfully the Freescale MDS boards do have logic
analyz
David Hawkins wrote:
> Whatever was written to i2c_bus_speed[0] was never actually
> written, since the write occurs to flash before relocation,
> so whatever the intent of the write was, needs to be fixed.
Prior to relocation, the value of i2c_bus_speed[] is irrelevant. All that
matter is that
In message <[EMAIL PROTECTED]> you wrote:
>
> There are at least two problems with your U-Boot 1.1.3 configuration:
>
> > #define CONFIG_ETHADDROO:11:22:33:44:55/* board MAC addr
> */
>
> The first byte "OO" is two capital Os; perhaps "00" was the intended
> first byte of the MAC add
In message <[EMAIL PROTECTED]> you wrote:
>
> > Which exact driver are you referring to? If any driver has such a bug,
> > it should be fixed.
>
> drivers/i2c/fsl_i2c.c
>
> The function is i2c_init(). I recently posted a patch that added this line
> of code:
>
> i2c_bus_speed[0] = set_i
This patch allows booting from FLASH the ML507 board
by Xilinx.
Previously, u-boot needed to be loaded from JTAG or a Sytem ACE
CF
Signed-off-by: Ricardo Ribalda Delgado <[EMAIL PROTECTED]>
---
MAKEALL |1 +
Makefile |8 ++
board/xilin
vijay vijay wrote:
> I am using Denx u-boot 1.1.3 for MPC 870 board.
> I ported it for our board with mpc870 processor and I got the
> u-boot (->) prompt.
> UART interface is working fine but Ethernet interface (motfec)
> is not up yet.
ub> ping 10.10.10.4
> TX timeout
> TX timeout
> ping faile
David Hawkins wrote:
> Hi Jerry,
[snip]
>> Most processors available today have debug registers. If the
>> processor used on a given target has a debug register set and the
>> registers can be set to trigger on a write to a range, that would give
>> you an exception. You would not necessarily
Hi Timur,
> I'm working on a patch that blocks i2c_init() from writing to
> global variables before relocation has occurred. But if
> you're saying that this patch should not be necessary,
> then that would be better.
The I2C patch is necessary.
Whatever was written to i2c_bus_speed[0] was neve
Hi Jerry,
>> The fix will also not expose the accidental introduction
>> of flash writes in the future, it'll just stop those
>> writes from having any effect.
>
> IOW, it simply hides the bug. :-(
Yeah, I didn't like that as a solution either.
>> It would be nicer to generate an exception if
Hi Wolfgang,
>> We recently debugged a problem where a Flash write on
>> MPC8349E and MPC8349EA processor boards was accidentally
>> occurring during board initialization.
>
> A write to flash should not matter at all.
Thats what I thought, until I saw the logic analyzer
trace show otherwise ...
Hello,
I am currently trying to get u-boot to work on our mx31 litekit from logic
pd. Everything is compiling just fine and we are able to load our board with
our BDI3000, but executing u-boot doesn't result in the u-boot prompt or
anything else.
I noticed that the litektit's config.mk file has a
Wolfgang Denk wrote:
> Which exact driver are you referring to? If any driver has such a bug,
> it should be fixed.
drivers/i2c/fsl_i2c.c
The function is i2c_init(). I recently posted a patch that added this line of
code:
i2c_bus_speed[0] = set_i2c_bus_speed(dev, gd->i2c1_clk, speed);
On Mon, 2008-07-21 at 08:13 -0400, Steven Bass wrote:
> I've just become involved in a project which is using U-boot as the
> bootloader. This is a smallish embedded system. I'm trying to find the
> right way to handle the use of U-boot. What sort of acknowledgements,
> source code availability,
> Your patch is line-wrapped and thus unusable. Please fix your mailer
> setup and resubmit.
>
> Best regards,
>
> Wolfgang Denk
>
> --
Sorry, it shouldn't have done that. :-/
Adrian
--
Linux Software Engineer | EuroTech, Inc. | www.eurotech-inc.com
---
In message <[EMAIL PROTECTED]> you wrote:
>
> I've just become involved in a project which is using U-boot as the
> bootloader. This is a smallish embedded system. I'm trying to find the
> right way to handle the use of U-boot. What sort of acknowledgements,
> source code availability, etc. are ex
Hi Markus,
Thanks for the valuable Help.
Thanks and Regards,
Shivdas Gujare
On Mon, Jul 21, 2008 at 4:15 PM, Markus Klotzbücher <[EMAIL PROTECTED]> wrote:
> "Shivdas Gujare" <[EMAIL PROTECTED]> writes:
>
> > I am working on getting USB-uboot working on OSK5912.
> > from linux USB gadget "devi
I've just become involved in a project which is using U-boot as the
bootloader. This is a smallish embedded system. I'm trying to find the
right way to handle the use of U-boot. What sort of acknowledgements,
source code availability, etc. are expected here.
U-boot isn't ever visible to the user
David Hawkins wrote:
> Hi all,
>
> We recently debugged a problem where a Flash write on
> MPC8349E and MPC8349EA processor boards was accidentally
> occurring during board initialization.
>
> Under the right conditions, the write appears to put
> the flash into a command-mode, rather than read-d
"Shivdas Gujare" <[EMAIL PROTECTED]> writes:
> I am working on getting USB-uboot working on OSK5912.
> from linux USB gadget "device controller drivers" (i.e.
> kernel/drivers/usb/gadget/) it looks like
> USB core for omap1510 and OSK5912 is same..But not sure, please confirm
No idea. You will ha
Sebastian Siewior wrote:
> * Wolfgang Grandegger | 2008-07-15 13:28:40 [+0200]:
>
>> Sebastian Siewior wrote:
>>> * Andy Fleming | 2008-07-14 19:27:08 [-0500]:
>>>
On Mon, Jul 14, 2008 at 5:54 AM, Sebastian Siewior
<[EMAIL PROTECTED]> wrote:
> The default value for the MxMR register
Baby cut from mother's womb
http://nuovacifet.it/begin.html
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coo
Hi,
> >>Are you going to add a board which will use it?
> >> Right now i am using it on arm Versatile board. Should i send a
patch
> >> to that also
> >>If you do I can test it
> >>Regards
> >>Peter
Please find attached my changes to arm versatile config & board file to
enable rtc module
52 matches
Mail list logo
