Hi,
This concept is very good.
But I have one question. I think need to call mmc_init() one more, right?
how did you save the boot time(200ms)?
On 11/29/2012 10:21 AM, Simon Glass wrote:
From: Che-Liang Chiou clch...@chromium.org
Most of time that MMC driver spends on initializing a device
Hi,
I did following steps to compile u-boot on x86-64.
U-boot Build procedure
The following command sequence is used to build the u-boot for the particular
board.
-To remove ALL files made by by make,configure
make distclean
To configure the x86 32 bit based board for the target we
2012/11/29 Bo Shen voice.s...@atmel.com:
Hi !
As port C doesn't support EHCI, so, I think we should deal with this
carefully.
---8---
#if OHCI
#else EHCI
#endif
---8---
I think this will be better.
yes, you're right, I'll change that
___
U-Boot
From: Richard Genoud richard.gen...@gmail.com
This small patchset is based on current master (
178d0cc1a4c73c3341afbeb2a93b172de8c96bd1 )
It enables usb on at91sam9x5ek boards.
Tested on at91sam9x5ek with a sam9g35 CPU (+ usb key and mouse)
By default the 3 USB 1.1 ports (A, B and C) are
From: Richard Genoud richard.gen...@gmail.com
Signed-off-by: Richard Genoud richard.gen...@gmail.com
---
include/configs/at91sam9x5ek.h |6 +-
1 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/include/configs/at91sam9x5ek.h b/include/configs/at91sam9x5ek.h
index
From: Richard Genoud richard.gen...@gmail.com
Signed-off-by: Richard Genoud richard.gen...@gmail.com
---
arch/arm/cpu/arm926ejs/at91/at91sam9x5_devices.c | 13 +
arch/arm/include/asm/arch-at91/at91sam9x5.h |2 ++
board/atmel/at91sam9x5ek/at91sam9x5ek.c |3 +++
From: Richard Genoud richard.gen...@gmail.com
Signed-off-by: Richard Genoud richard.gen...@gmail.com
---
include/configs/at91sam9x5ek.h | 23 +++
1 files changed, 23 insertions(+), 0 deletions(-)
diff --git a/include/configs/at91sam9x5ek.h b/include/configs/at91sam9x5ek.h
From: Richard Genoud richard.gen...@gmail.com
Signed-off-by: Richard Genoud richard.gen...@gmail.com
---
doc/README.usb |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/doc/README.usb b/doc/README.usb
index ef1d6ba..b4c3ef5 100644
--- a/doc/README.usb
+++
On 11/30/2012 17:18, richard.gen...@gmail.com wrote:
From: Richard Genoud richard.gen...@gmail.com
Signed-off-by: Richard Genoud richard.gen...@gmail.com
Acked-by: Bo Shen voice.s...@atmel.com
---
arch/arm/cpu/arm926ejs/at91/at91sam9x5_devices.c | 13 +
On 11/30/2012 17:18, richard.gen...@gmail.com wrote:
From: Richard Genoud richard.gen...@gmail.com
Signed-off-by: Richard Genoud richard.gen...@gmail.com
Acked-by: Bo Shen voice.s...@atmel.com
Best Regards,
Bo Shen
---
include/configs/at91sam9x5ek.h |6 +-
1 files changed, 5
On 11/30/2012 17:18, richard.gen...@gmail.com wrote:
From: Richard Genoud richard.gen...@gmail.com
Signed-off-by: Richard Genoud richard.gen...@gmail.com
Acked-by: Bo Shen voice.s...@atmel.com
Best Regards,
Bo Shen
---
include/configs/at91sam9x5ek.h | 23 +++
1
On 11/21/2012 10:24 AM, Wolfgang Denk wrote:
Dear Vipin,
In message50a0d0eb.4080...@st.com you wrote:
The ssh key is as below
THnaks a lot. The repository should be ready for your use now. Sorry
it took so long.
Please feel free to contact me directly if there should be any
problems.
Dear Armando Visconti,
In message 50b89534.6040...@st.com you wrote:
Not sure what are next steps for this patchset.
Is someone going to review it, or part of it?
Or is Vipin expected to do something on the repository
assigned to him (maybe he already did)?
Vipin volunteered as custodian,
The elftosb tool is now called with -d switch, which produces debug
output to the stdout. The debug output is completely useless for
regular operation, so silence it.
Signed-off-by: Marek Vasut ma...@denx.de
Cc: Stefano Babic sba...@denx.de
Cc: Fabio Estevam fabio.este...@freescale.com
---
This algorithm computes the values of TIMING{0,1,2} registers for the
MX28 I2C block. This algorithm was derived by using a scope, but the
result seems correct.
The resulting values programmed into the registers do not correlate
with the contents of the datasheet. When using the values from the
On 11/30/2012 01:34 PM, Wolfgang Denk wrote:
Dear Armando Visconti,
In message50b89534.6040...@st.com you wrote:
Not sure what are next steps for this patchset.
Is someone going to review it, or part of it?
Or is Vipin expected to do something on the repository
assigned to him (maybe he
Dear Marek Vasut,
In message 1354280910-17539-1-git-send-email-ma...@denx.de you wrote:
This algorithm computes the values of TIMING{0,1,2} registers for the
MX28 I2C block. This algorithm was derived by using a scope, but the
result seems correct.
Thanks! I like that!
...
+ uint32_t
Dear Wolfgang Denk,
Dear Marek Vasut,
In message 1354280910-17539-1-git-send-email-ma...@denx.de you wrote:
This algorithm computes the values of TIMING{0,1,2} registers for the
MX28 I2C block. This algorithm was derived by using a scope, but the
result seems correct.
Thanks! I like
Implement common function to setup the VDDIO, VDDD and VDDA voltage.
Right now, there are two almost identical functions to setup VDDIO
and VDDD, which is prone to breakage. Pull out the differences into
constant structure and pass them as an argument to the common function.
Moreover, the
The memory setup code adjusted the VDDD voltage. Remove this adjustment
and configure the VDDD voltage correctly in the power supply setup code.
Signed-off-by: Marek Vasut ma...@denx.de
Cc: Stefano Babic sba...@denx.de
Cc: Fabio Estevam fabio.este...@freescale.com
---
This algorithm computes the values of TIMING{0,1,2} registers for the
MX28 I2C block. This algorithm was derived by using a scope, but the
result seems correct.
The resulting values programmed into the registers do not correlate
with the contents in datasheet. When using the values from the
From: Stefan Reinauer reina...@chromium.org
Add a basic driver for the coreboot framebuffer.
Signed-off-by: Stefan Reinauer reina...@chromium.org
Signed-off-by: Simon Glass s...@chromium.org
---
Changes in v3:
- Update to avoid using gd which is now a #define
Changes in v2: None
Third take of USB + DFU updates.
Pantelis Antoniou (9):
usb: Fix bug when both DFU ETHER are defined
g_dnl: Issue connect/disconnect as appropriate
g_dnl: Properly terminate string list.
dfu: Only perform DFU board_usb_init() for TRATS
dfu: Fix crash when wrong number of arguments
Call usb_gadget_connect/usb_gadget_disconnect in g_dnl_bind/g_dnl_unbind.
Signed-off-by: Pantelis Antoniou pa...@antoniou-consulting.com
---
drivers/usb/gadget/g_dnl.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/drivers/usb/gadget/g_dnl.c
Well, not terminating the list causes very interesting crashes.
As in changing the vendor product ID crashes. Fun.
Signed-off-by: Pantelis Antoniou pa...@antoniou-consulting.com
---
drivers/usb/gadget/g_dnl.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/gadget/g_dnl.c
When both CONFIG_USB_GADGET CONFIG_USB_ETHER are defined
the makefile links objects twice.
The cleanest way to fix is to use a new define, CONFIG_USB_UTIL
which must be defined when either CONFIG_USB_ETHER or
CONFIG_USB_GADGET are defined.
All affected boards have been modified as well.
USB initialization shouldn't happen for all the boards.
Signed-off-by: Pantelis Antoniou pa...@antoniou-consulting.com
---
common/cmd_dfu.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/common/cmd_dfu.c b/common/cmd_dfu.c
index 01d6b3a..327c738 100644
--- a/common/cmd_dfu.c
+++
DFU is a bit peculiar. It needs to hook to composite setup and
return it's function descriptor.
So when get-descriptor request comes with a type of DFU_DT_FUNC
we iterate over the configs, and functions, and when we find
the DFU function we call the setup method which is prepared
to return the
Fix obvious crash when not enough arguments are given to the dfu
command.
Signed-off-by: Pantelis Antoniou pa...@antoniou-consulting.com
---
common/cmd_dfu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/common/cmd_dfu.c b/common/cmd_dfu.c
index 327c738..83ef324 100644
---
Zero out timeout value; letting it filled with undefined values
ends up with the dfu host hanging.
Signed-off-by: Pantelis Antoniou pa...@antoniou-consulting.com
---
drivers/usb/gadget/f_dfu.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/usb/gadget/f_dfu.c
Dealing with raw block numbers with the dfu is very annoying.
Introduce a partition method.
Signed-off-by: Pantelis Antoniou pa...@antoniou-consulting.com
---
drivers/dfu/dfu_mmc.c | 31 +++
1 file changed, 31 insertions(+)
diff --git a/drivers/dfu/dfu_mmc.c
We didn't support upload/download larger than available memory.
This is pretty bad when you have to update your root filesystem for
example.
This patch removes the limitation (and the crashes when you transfered
any file larger than 4MB).
On top of that reduces the huge dfu buffer from 4MB to
Hi Pantelis,
One request:
Please stick to following guidelines:
http://www.denx.de/wiki/U-Boot/Patches
USB initialization shouldn't happen for all the boards.
Signed-off-by: Pantelis Antoniou pa...@antoniou-consulting.com
---
common/cmd_dfu.c | 3 +++
1 file changed, 3 insertions(+)
The MXS SPL didn't mark local functions static. Fix it. This also makes the
SPL smaller by roughly 300 bytes.
Signed-off-by: Marek Vasut ma...@denx.de
Cc: Stefano Babic sba...@denx.de
Cc: Fabio Estevam fabio.este...@freescale.com
---
arch/arm/cpu/arm926ejs/mxs/spl_boot.c |4 +-
Hi Pantelis,
Fix obvious crash when not enough arguments are given to the dfu
command.
Signed-off-by: Pantelis Antoniou pa...@antoniou-consulting.com
---
common/cmd_dfu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/common/cmd_dfu.c b/common/cmd_dfu.c
index
Third take of USB + DFU updates.
Changelog for the pendants:
changes from v2:
* Handle large transfers properly take #2
* Different method of avoid double linking of
usb gadget usb ether.
changes from v1:
* Properly terminate terminate string list.
* Handle large transfers properly take #1
Call usb_gadget_connect/usb_gadget_disconnect in g_dnl_bind/g_dnl_unbind.
Signed-off-by: Pantelis Antoniou pa...@antoniou-consulting.com
---
drivers/usb/gadget/g_dnl.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/drivers/usb/gadget/g_dnl.c
When both CONFIG_USB_GADGET CONFIG_USB_ETHER are defined
the makefile links objects twice.
The cleanest way to fix is to use a new define, CONFIG_USB_UTIL
which must be defined when either CONFIG_USB_ETHER or
CONFIG_USB_GADGET are defined.
All affected boards have been modified as well.
Well, not terminating the list causes very interesting crashes.
As in changing the vendor product ID crashes. Fun.
Signed-off-by: Pantelis Antoniou pa...@antoniou-consulting.com
---
drivers/usb/gadget/g_dnl.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/gadget/g_dnl.c
USB initialization shouldn't happen for all the boards.
Signed-off-by: Pantelis Antoniou pa...@antoniou-consulting.com
---
common/cmd_dfu.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/common/cmd_dfu.c b/common/cmd_dfu.c
index 01d6b3a..327c738 100644
--- a/common/cmd_dfu.c
+++
DFU is a bit peculiar. It needs to hook to composite setup and
return it's function descriptor.
So when get-descriptor request comes with a type of DFU_DT_FUNC
we iterate over the configs, and functions, and when we find
the DFU function we call the setup method which is prepared
to return the
Fix obvious crash when not enough arguments are given to the dfu
command.
Signed-off-by: Pantelis Antoniou pa...@antoniou-consulting.com
---
common/cmd_dfu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/common/cmd_dfu.c b/common/cmd_dfu.c
index 327c738..83ef324 100644
---
Dealing with raw block numbers with the dfu is very annoying.
Introduce a partition method.
Signed-off-by: Pantelis Antoniou pa...@antoniou-consulting.com
---
drivers/dfu/dfu_mmc.c | 31 +++
1 file changed, 31 insertions(+)
diff --git a/drivers/dfu/dfu_mmc.c
Zero out timeout value; letting it filled with undefined values
ends up with the dfu host hanging.
Signed-off-by: Pantelis Antoniou pa...@antoniou-consulting.com
---
drivers/usb/gadget/f_dfu.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/usb/gadget/f_dfu.c
We didn't support upload/download larger than available memory.
This is pretty bad when you have to update your root filesystem for
example.
This patch removes the limitation (and the crashes when you transfered
any file larger than 4MB).
On top of that reduces the huge dfu buffer from 4MB to
On Fri, Nov 30, 2012 at 11:04 AM, Marek Vasut ma...@denx.de wrote:
The elftosb tool is now called with -d switch, which produces debug
output to the stdout. The debug output is completely useless for
regular operation, so silence it.
Signed-off-by: Marek Vasut ma...@denx.de
Cc: Stefano
On Fri, Nov 30, 2012 at 1:22 PM, Marek Vasut ma...@denx.de wrote:
Implement common function to setup the VDDIO, VDDD and VDDA voltage.
Right now, there are two almost identical functions to setup VDDIO
and VDDD, which is prone to breakage. Pull out the differences into
constant structure and
Dear Otavio Salvador,
On Fri, Nov 30, 2012 at 1:22 PM, Marek Vasut ma...@denx.de wrote:
Implement common function to setup the VDDIO, VDDD and VDDA voltage.
Right now, there are two almost identical functions to setup VDDIO
and VDDD, which is prone to breakage. Pull out the differences
On Fri, Nov 30, 2012 at 4:35 PM, Marek Vasut ma...@denx.de wrote:
Dear Otavio Salvador,
On Fri, Nov 30, 2012 at 1:22 PM, Marek Vasut ma...@denx.de wrote:
Implement common function to setup the VDDIO, VDDD and VDDA voltage.
Right now, there are two almost identical functions to setup
Hi Albert,
On Wed, Nov 28, 2012 at 2:34 PM, Albert ARIBAUD
albert.u.b...@aribaud.net wrote:
Hi Simon,
On Wed, 28 Nov 2012 13:18:57 -0800, Simon Glass s...@chromium.org
wrote:
Hi Albert,
On Tue, Nov 27, 2012 at 4:43 AM, Albert ARIBAUD
albert.u.b...@aribaud.net wrote:
Move all the C
From: Gabe Black gabebl...@chromium.org
It may be necessary to know where the TLB area ends as well as where it
starts. This allows board code to complete a secure memory erase without
destroying the page tables.
Signed-off-by: Gabe Black gabebl...@google.com
Signed-off-by: Simon Glass
This option displays board info after stdio is running, so that it will
appear on the LCD. If it is displayed earlier, the board info will appear
on the serial console but not on the LCD.
Here follows a blow-by-blow description.
1a. Without CONFIG_DISPLAY_BOARDINFO_LATE, on serial:
U-Boot
We want to use the fdt inside board_early_init_f(), so check for its
presence earlier in the pre-reloc init sequence.
So far ARM and microblaze are the only only ones that use
CONFIG_OF_CONTROL. Microblaze does not have the same init loop, and in
particular does not have the board_early_init_f()
From: Arun Mankuzhi aru...@samsung.com
In Cortex-A15 architecture, when we run cache invalidate
the cache clean operation executes automatically.
So if there are any dirty cache lines before disabling the L2 cache
these will be synchronized with the main memory when
invalidate_dcache_all() runs
Add a short note about this in the README.
Signed-off-by: Simon Glass s...@chromium.org
---
Changes in v2:
- Split out CONFIG_DISPLAY_BOARDINFO README change into separate commit
README |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/README b/README
index
Some boards want to report more than just memory size. For example, it
might be useful to display the memory type (DDR2, DDR3) or manufacturer.
Add a weak function to support this requirement, accessed through a new
'meminfo' command.
Any example of the DRAM: output is below, just for
From: Tom Wai-Hong Tam waih...@chromium.org
SPL u-boot may call do_reset() which depends on interrupts.o and reset.o.
So make them also appear in SPL.
Signed-off-by: Tom Wai-Hong Tam waih...@chromium.org
Signed-off-by: Simon Glass s...@chromium.org
---
Changes in v2: None
arch/arm/lib/Makefile
The timer may be inited in arch_cpu_init() so it is not safe to make a
bootstage mark before this is called. Arrange the code to fix this.
Note: The question was raised as to why we don't keep all archs in sync.
PowerPC doesn't have specific bootstage markers at present (although it
does use boot
From: Taylor Hutt th...@chromium.org
The two modified lines were indented with spaces.
They are now indented with tabs.
Signed-off-by: Taylor Hutt th...@chromium.org
Signed-off-by: Simon Glass s...@chromium.org
---
Changes in v2: None
arch/arm/lib/board.c |4 ++--
1 files changed, 2
This option delays loading of the environment until later, so that only the
default environment will be available to U-Boot.
This can address the security risk of untrusted data being used during boot.
Any time you load untrusted data you expose yourself to a bug in the
code. The attacker gets
Hi,
On Thu, Nov 29, 2012 at 7:20 AM, Jae hoon Chung jh80.ch...@gmail.com wrote:
Hi Simon,
Is it saved the 200ms? Could you tell me your environment?
I will check this patch..and share the result.
The environment is snow (Samsung ARM Chromebook). The time save only
comes from not waiting for
Hi Jaehoon,
On Fri, Nov 30, 2012 at 12:25 AM, Jaehoon Chung jh80.ch...@samsung.com wrote:
Hi,
This concept is very good.
But I have one question. I think need to call mmc_init() one more, right?
how did you save the boot time(200ms)?
On 11/29/2012 10:21 AM, Simon Glass wrote:
From:
Hi Allan Drassal,
Frankly, I'm not in practice faced ar71xx processors in labs, but I
can give details on experience with the ar724x CPUs.
First we need to determine are fully is support in ar71xx.cfg file for
your device.
You need connect to the JTAG and switch the device in halt mode. Next
Add support for SST 4KB sector granularity.
Many recent SST flashes, i.e. SST39VF3201B and similar of this family
are declared CFI-conformant from SST. They support CFI query, but implement
2 different sector sizes in the same memory: a 64KB sector (they call it
block, std AMD erase cmd=0x30),
There are cases that we want to support different settings (or maybe
even different aliases) for different projects. Add support for this
by:
* Adding detection for two big projects: U-Boot and Linux.
* Adding default settings for Linux (U-Boot is already good with the
standard patman
If we're sending a cover letter make sure to CC everyone that we're
CCing on each of the individual patches.
Signed-off-by: Doug Anderson diand...@chromium.org
---
tools/patman/patman.py |2 +-
tools/patman/series.py | 12 +++-
2 files changed, 12 insertions(+), 2 deletions(-)
For Linux the best way to figure out where to send a patch is with the
get_maintainer.pl script. Add support for calling it from patman.
Support is added unconditionally for scripts/get_maintainer.pl in
case it is helpful for any other projects.
Signed-off-by: Doug Anderson diand...@chromium.org
This patch adds support for a [settings] section in the .patman file.
In this section you can add settings that will affect the default
values for command-line options.
Support is added in a generic way such that any setting can be updated
by just referring to the dest of the option that is
The settings modules now has doctests, so run them.
Signed-off-by: Doug Anderson diand...@chromium.org
---
tools/patman/patman.py |5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/tools/patman/patman.py b/tools/patman/patman.py
index 54a252e..6825de4 100755
---
Currently we go through and generate the CC list for patches twice.
This gets slow when (in a future CL) we add a call to
get_maintainer.pl on Linux. Instead of doing things twice, just cache
the CC list when it is first generated.
Signed-off-by: Doug Anderson diand...@chromium.org
---
On Fri, Nov 30, 2012 at 3:01 PM, Simon Glass s...@chromium.org wrote:
This option delays loading of the environment until later, so that only the
default environment will be available to U-Boot.
This can address the security risk of untrusted data being used during boot.
Any time you load
Hello Marek,
On 30.11.2012 16:28, Marek Vasut wrote:
This algorithm computes the values of TIMING{0,1,2} registers for the
MX28 I2C block. This algorithm was derived by using a scope, but the
result seems correct.
The resulting values programmed into the registers do not correlate
with the
Dear Heiko Schocher,
Hello Marek,
[...]
diff --git a/drivers/i2c/mxs_i2c.c b/drivers/i2c/mxs_i2c.c
index 006fb91..b040535 100644
--- a/drivers/i2c/mxs_i2c.c
+++ b/drivers/i2c/mxs_i2c.c
@@ -28,6 +28,7 @@
#includecommon.h
#includemalloc.h
+#includei2c.h
Hi Dmytro,
Thanks for your detailed response. I corrected some details in the ar71xx.cfg
file and am posting them below this message.
With this, I am convinced that my JTAG interface is working and the DRAM
controller is getting setup correctly.
Now, I am just needing some code to load into
The I2C block reset configures the I2C bus speed to strange value.
Read the I2C speed from the block before reseting the block and
restore it afterwards, so the I2C operates correctly. This issue
can be replicated by doing unsuccessful I2C transfer, after such
transfer finishes, the I2C block
This algorithm computes the values of TIMING{0,1,2} registers for the
MX28 I2C block. This algorithm was derived by using a scope, but the
result seems correct.
The resulting values programmed into the registers do not correlate
with the contents in datasheet. When using the values from the
Dear richard.gen...@gmail.com,
From: Richard Genoud richard.gen...@gmail.com
Signed-off-by: Richard Genoud richard.gen...@gmail.com
Applied this patch, thanks. Next time please Cc me, that way you have better
chance I'll notice the patch right away ;-)
---
doc/README.usb |2 +-
1
Dear Pantelis Antoniou,
When both CONFIG_USB_GADGET CONFIG_USB_ETHER are defined
the makefile links objects twice.
The cleanest way to fix is to use a new define, CONFIG_USB_UTIL
which must be defined when either CONFIG_USB_ETHER or
CONFIG_USB_GADGET are defined.
All affected boards
Dear Pantelis Antoniou,
USB initialization shouldn't happen for all the boards.
Signed-off-by: Pantelis Antoniou pa...@antoniou-consulting.com
---
common/cmd_dfu.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/common/cmd_dfu.c b/common/cmd_dfu.c
index 01d6b3a..327c738 100644
Dear Pantelis Antoniou,
Third take of USB + DFU updates.
Changelog for the pendants:
changes from v2:
* Handle large transfers properly take #2
* Different method of avoid double linking of
usb gadget usb ether.
changes from v1:
* Properly terminate terminate string list.
*
I think I made a little more progress...
Using the following commands I can get output from the UART...
# set GPIO 9 10 as UART
mww 0xb804 0x400
mww 0xb8040028 0x100
mww 0xb8020004 0x0
mww 0xb802000c 0x83
mww 0xb802 0x51
mww 0xb8020004 0x0
mww 0xb802000c 0x3
mww
81 matches
Mail list logo
