On 25/11/2012 01:21, Marek Vasut wrote:
> Add register definitions for the i.MX23 power control block and
> clock control block. These are essential for the basic bootstrap
> of the i.MX23. Also, properly include them in imx-regs.h .
>
> Signed-off-by: Marek Vasut
> Cc: Stefano Babic
> ---
Hi M
On 30/11/2012 14:04, Marek Vasut 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
> Cc: Stefano Babic
> Cc: Fabio Estevam
> ---
> Ma
On 28/11/2012 21:40, Troy Kisky wrote:
> On 11/28/2012 2:39 AM, Wolfgang Denk wrote:
>> Dear Troy Kisky,
>>
>> In message
>> <1354066303-29762-9-git-send-email-troy.ki...@boundarydevices.com> you
>> wrote:
>>> Before, only 1 write_dcd_command table was built.
>>> Now, a new table is built when the
On 30/11/2012 16:22, Marek Vasut 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 pass them as an argument
On 30/11/2012 16:22, Marek Vasut wrote:
> 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
> Cc: Stefano Babic
> Cc: Fabio Estevam
> ---
> arch/arm/cpu/arm926ejs/mxs
On 30/11/2012 18:09, Marek Vasut wrote:
> 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
> Cc: Stefano Babic
> Cc: Fabio Estevam
> ---
Hi Marek,
this should be better part of the previous patchse
This patch set add support for the Marvell Dove 88AP510 SoC and
the SolidRun CuBox board based on that SoC. The patch set is divided
into the four following sections:
(1) Patches 1-5:
Add support for the Dove SoC and related drivers. Where possible
drivers from Marvell Kirkwood are reused (mvsata,
This adds a gpio driver for Marvell Orion SoCs, i.e. orion5x, kirkwood,
dove. This is based on kw_gpio but as gpio capabilities depend heavily
on the mpp configuration for dove, it allows to set gpi/gpo capabilities
from mpp. This should be compatible with the current kw_gpio and porting
mpp of kir
Dove SoC also uses mvsata, therefore add a SoC specific include to
allow to reuse the mvsata ide driver.
Signed-off-by: Sebastian Hesselbarth
---
Cc: u-boot@lists.denx.de
Cc: Sebastian Hesselbarth
Cc: Rabeeh Khoury
Cc: Albert Aribaud
Cc: Prafulla Wadaskar
Cc: Andy Fleming
Cc: Joe Hershberger
This adds PHY initialization for Marvell Alaska 88E1310 PHY.
Signed-off-by: Sebastian Hesselbarth
---
Cc: u-boot@lists.denx.de
Cc: Sebastian Hesselbarth
Cc: Rabeeh Khoury
Cc: Albert Aribaud
Cc: Prafulla Wadaskar
Cc: Andy Fleming
Cc: Joe Hershberger
Cc: Daniel Stodden
Cc: Luka Perkov
---
This adds an SPI driver found on Marvell Orion SoCs. This driver is
taken from kirkwood_spi but removes mpp configuration as dove has
dedicated spi pins. To have a common driver for orion5x, kirkwood,
and dove, mpp configuration should be handled in some cpu/board-specific
setup.
Signed-off-by: Se
This add phylib support to the Marvell GBE driver.
Signed-off-by: Sebastian Hesselbarth
---
Cc: u-boot@lists.denx.de
Cc: Sebastian Hesselbarth
Cc: Rabeeh Khoury
Cc: Albert Aribaud
Cc: Prafulla Wadaskar
Cc: Andy Fleming
Cc: Joe Hershberger
Cc: Daniel Stodden
Cc: Luka Perkov
---
drivers/ne
Marvell Dove also uses mvgbe as ethernet driver, therefore add support
for Dove to reuse the current driver.
Signed-off-by: Sebastian Hesselbarth
---
Cc: u-boot@lists.denx.de
Cc: Sebastian Hesselbarth
Cc: Rabeeh Khoury
Cc: Albert Aribaud
Cc: Prafulla Wadaskar
Cc: Andy Fleming
Cc: Joe Hershbe
With latest support for Marvell Dove SoC, add the SolidRun CuBox as
the very first board with that SoC.
Signed-off-by: Sebastian Hesselbarth
---
Changelog:
v1->v2:
- add MAINTAINERS entry and fix a typo
Cc: u-boot@lists.denx.de
Cc: Sebastian Hesselbarth
Cc: Rabeeh Khoury
Cc: Albert Aribaud
Cc
On Dove kwboot can also be used to boot an u-boot image into RAM.
In contrast to Kirkwood, Dove does not support the UART boot mode
sequence but requires the UART boot mode to be selected through
strap pins. The SolidRun CuBox has a push button to allow uart
boot mode but fails on the boot sequence
Lanes mux currently is configured in eth.c when initializing FMAN ethernet
ports, but SRIO and PCIe also need lanes mux, so we move the lanes mux to
p2041rdb.c which implements a board-specific initialization and will be
called at early stage.
Signed-off-by: Shaohui Xie
---
board/freescale/p2041
Dear Stefano Babic,
> On 30/11/2012 18:09, Marek Vasut wrote:
> > 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
> > Cc: Stefano Babic
> > Cc: Fabio Estevam
> > ---
>
> Hi Marek,
>
> this
Dear All,
> Several fixes for ext4write command including:
> - compiler warnings suppress
> - lldiv() and do_div() instead of "plain" / and % operands for 64-32
> bits
> - Proper initialization of dev_desc
>
> Lukasz Majewski (4):
> fs:ext4:write: Add lldiv and do_div to perform 64-32 bits div
Hi Simon,
Will add the other two SPI ports and submit the patches.
Regards,
Rajeshwari Shinde.
On Tue, Dec 4, 2012 at 6:37 AM, Simon Glass wrote:
> Hi Rajeshwari,
>
> On Mon, Dec 3, 2012 at 2:40 AM, Rajeshwari Shinde
> wrote:
>> This patch adds aliases for SPI.
>>
>> Signed-off-by: Rajeshwari
On Tue, Dec 4, 2012 at 6:45 AM, Simon Glass wrote:
> On Mon, Dec 3, 2012 at 4:12 AM, Rajeshwari Shinde
> wrote:
>> Add device node for MAX77686
>>
>> Signed-off-by: Rajeshwari Shinde
>> ---
>> board/samsung/dts/exynos5250-smdk5250.dts |7 +++
>> 1 files changed, 7 insertions(+), 0 delet
On Tue, Dec 4, 2012 at 5:59 AM, Stefano Babic wrote:
> On 25/11/2012 01:21, Marek Vasut wrote:
> > Add register definitions for the i.MX23 power control block and
> > clock control block. These are essential for the basic bootstrap
> > of the i.MX23. Also, properly include them in imx-regs.h .
>
Dear All,
How to access u-boot environment variables from kernel space or user
space in P1012 processor.
The variables required to be accessed from uboot environment section
are:
eth1addr
serverip
Note: Kernel version = 2.6.35
Regards
Manukumar
_
Signed-off-by: Richard Genoud
---
fs/fat/fat.c |8
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/fs/fat/fat.c b/fs/fat/fat.c
index 393c378..defdd74 100644
--- a/fs/fat/fat.c
+++ b/fs/fat/fat.c
@@ -589,7 +589,9 @@ static dir_entry *get_dentfromdir(fsdata *mydata, int
Use a generic 'dram_vals[]' array that has the full initialization
sequence and rename the initialization method so it doesn't has a
frequency on its name.
Signed-off-by: Otavio Salvador
---
arch/arm/cpu/arm926ejs/mxs/spl_mem_init.c | 19 +--
1 file changed, 13 insertions(+), 6
On Tue, Dec 4, 2012 at 1:04 PM, Manukumar wrote:
> Dear All,
>
> How to access u-boot environment variables from kernel space or user
> space in P1012 processor.
>
> The variables required to be accessed from uboot environment section
> are:
>
> eth1addr
You can get the MAC address from related r
Dear Richard Genoud,
Please provide a reasonable commit message. Why is this needed?
I really dislike the amount of added #ifdefs :(
[...]
Best regards,
Marek Vasut
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-bo
2012/12/4 Marek Vasut :
> Dear Richard Genoud,
>
> Please provide a reasonable commit message. Why is this needed?
hi,
You're right, my commit message is nearly inexistent.. sorry.
This is needed in the case where we don't want the VFAT support (for
whatever reason).
in this case, we #undef CONFIG
On 04/12/2012 14:04, Richard Genoud wrote:
> Signed-off-by: Richard Genoud
> ---
> fs/fat/fat.c |8
> 1 files changed, 8 insertions(+), 0 deletions(-)
>
> diff --git a/fs/fat/fat.c b/fs/fat/fat.c
> index 393c378..defdd74 100644
> --- a/fs/fat/fat.c
> +++ b/fs/fat/fat.c
> @@ -589,7 +
On 12/04/2012 07:24:51 AM, Yegor Yefremov wrote:
On Tue, Dec 4, 2012 at 1:04 PM, Manukumar
wrote:
> Dear All,
>
> How to access u-boot environment variables from kernel space or user
> space in P1012 processor.
>
> The variables required to be accessed from uboot environment section
> are:
>
>
On 12/04/2012 07:24:51 AM, Yegor Yefremov wrote:
> On Tue, Dec 4, 2012 at 1:04 PM, Manukumar
> wrote:
> > Dear All,
> >
> > How to access u-boot environment variables from kernel space or user
> > space in P1012 processor.
Have you looked at fw_printenv? I get output like this from it:
root:
Stephen,
On Mon, Dec 3, 2012 at 5:22 PM, Stephen Warren wrote:
> On 12/03/2012 04:45 PM, Tom Warren wrote:
>> Common Tegra files are in arch-tegra, shared between T20 and T30.
>> Tegra30-specific headers are in arch-tegra30. Note that some of
>> these will be filled in as more T30 support is adde
Stephen,
On Mon, Dec 3, 2012 at 5:34 PM, Stephen Warren wrote:
> On 12/03/2012 04:45 PM, Tom Warren wrote:
>> This provides SPL support for T30 boards - AVP early init, plus
>> CPU (A9) init/jump to main U-Boot.
>>
>> Some changes were made to Tegra20 cpu.c to move common routines
>> into tegra-c
Dear Graeme Russ,
In message
you
wrote:
>
> I've mentioned this before - I think gd is being abused. To me, gd
> should contain only data members that are explicitly required prior to
> SDRAM being initialised and BSS being available. It has become a bit
> of a 'well I need this variable every
Dear Simon,
In message
you wrote:
>
> The discussion at the time was here:
>
> http://patchwork.ozlabs.org/patch/146798/
>
> My previous effort to create a generic board init basically fell over
> on this point. Do you agree with the analysis and proposal on that
> thread?
Mostly; but some q
Dear Tom,
In message <20121203145414.GE15777@bill-the-cat> you wrote:
>
> > > - The change makes the code less readable. Reading "gd->arch."
> > > instead of plain "gd->" is no improvements, but rather vice versa.
> > > If we really go this way, this should be improved.
> >
> > Yes it would
Dear Simon Glass,
In message
you wrote:
>
> > To be honest, I think gd should only be a temporary structure used to
> > carry specific data through the initialisation process up to the point
> > BSS becomes available. With the 'early malloc' patches in the
> > pipeline, it might even be possibl
Dear Graeme Russ,
In message
you wrote:
>
> I agree. While gd->arch does look a bit 'ugly', it immediately unlocks
> the path forward to unifying the init loop. The x86 board.c would be a
> good start (IMNSHO) by simply making the init sequence arrays extern.
> From there we can tackle what rea
Stephen,
On Mon, Dec 3, 2012 at 5:42 PM, Stephen Warren wrote:
> On 12/03/2012 04:45 PM, Tom Warren wrote:
>> This patch adds basic Tegra30 (T30) build support - no specific
>> board is targeted.
>
>> diff --git a/board/nvidia/common/board.c b/board/nvidia/common/board.c
>
>> int board_early_ini
Stephen,
On Mon, Dec 3, 2012 at 5:53 PM, Stephen Warren wrote:
> On 12/03/2012 04:45 PM, Tom Warren wrote:
>> This build is stripped down. It boots to the command prompt.
>> GPIO is the only peripheral supported. Others TBD.
>>
>> include/configs/tegra-common.h now holds common config options
>>
Simon,
On Mon, Dec 3, 2012 at 6:01 PM, Simon Glass wrote:
> Hi Stephen,
>
> On Mon, Dec 3, 2012 at 4:57 PM, Stephen Warren wrote:
>> On 12/03/2012 05:49 PM, Simon Glass wrote:
>>> Hi Stephen,
>>>
>>> On Mon, Dec 3, 2012 at 4:40 PM, Stephen Warren
>>> wrote:
On 12/03/2012 04:45 PM, Tom War
Hi Tom,
Am Dienstag, den 04.12.2012, 13:22 -0700 schrieb Tom Warren:
[...]
>
> >
> >> +#define V_NS16550_CLK21600 /* 216MHz
> >> (pllp_out0) */
> >
> > I thought PLL_P ran at 408MHz on Tegra30? The kernel certainly sets it
> > up that way.
>
> See my previous r
Lucas,
On Tue, Dec 4, 2012 at 1:40 PM, Lucas Stach wrote:
> Hi Tom,
>
> Am Dienstag, den 04.12.2012, 13:22 -0700 schrieb Tom Warren:
> [...]
>>
>> >
>> >> +#define V_NS16550_CLK21600 /* 216MHz
>> >> (pllp_out0) */
>> >
>> > I thought PLL_P ran at 408MHz on Tegra
On 12/04/2012 01:40 PM, Lucas Stach wrote:
> Hi Tom,
>
> Am Dienstag, den 04.12.2012, 13:22 -0700 schrieb Tom Warren:
> [...]
>>
>>>
+#define V_NS16550_CLK21600 /* 216MHz
(pllp_out0) */
>>>
>>> I thought PLL_P ran at 408MHz on Tegra30? The kernel certai
On 12/04/2012 01:22 PM, Tom Warren wrote:
> Stephen,
>
> On Mon, Dec 3, 2012 at 5:53 PM, Stephen Warren wrote:
>> On 12/03/2012 04:45 PM, Tom Warren wrote:
>>> This build is stripped down. It boots to the command prompt.
>>> GPIO is the only peripheral supported. Others TBD.
>>>
>>> include/confi
Hi Wolfgang,
On Tue, Dec 4, 2012 at 11:27 AM, Wolfgang Denk wrote:
> Dear Graeme Russ,
>
> In message
> you
> wrote:
>>
>> I agree. While gd->arch does look a bit 'ugly', it immediately unlocks
>> the path forward to unifying the init loop. The x86 board.c would be a
>> good start (IMNSHO) by
Hi Wolfgang,
On Wed, Dec 5, 2012 at 6:25 AM, Wolfgang Denk wrote:
> Dear Simon Glass,
>
> In message
> you
> wrote:
>>
>> > To be honest, I think gd should only be a temporary structure used to
>> > carry specific data through the initialisation process up to the point
>> > BSS becomes availab
Implement a way to delete more than one variable at a time.
Signed-off-by: Joe Hershberger
---
Changes in v4:
- Implement delete
Changes in v3: None
Changes in v2: None
common/cmd_nvedit.c | 35 ---
1 file changed, 32 insertions(+), 3 deletions(-)
diff --git a/
Move the read of the old value to inside the check function. In some
cases it can be avoided all together and at the least the code is only
called from one place.
Also name the function and the callback to more clearly describe what
it does.
Pass the ENTRY instead of just the name for direct acc
When a variable with a registered callback is inserted, deleted, or
overwritten the callback is called and gives the system an opportunity
to do something in response to the change. It also has the opportunuty
to reject the change by returning non-zero.
The flags on variables can control their t
Remove the hard-coded baudrate handler and use a callback instead
Signed-off-by: Joe Hershberger
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
common/cmd_nvedit.c | 47 -
drivers/serial/serial.c | 70 +
Remove the hard-coded console handler and use a callback instead
Signed-off-by: Joe Hershberger
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
common/cmd_nvedit.c| 36 +++-
common/console.c | 44 +
Currently just validates variable types as decimal, hexidecimal,
boolean, ip address, and mac address.
If the entry is not found in the env ".flags", then look in the static
one. This allows the env to override the static definitions, but prevents
the need to have every definition in the environme
Use the variable access flags to implement the protection for ethaddr
and serial# instead of hard-coding them.
Signed-off-by: Joe Hershberger
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
common/env_flags.c | 19 ---
include/env_flags.h | 22 ++
The callbacks can be bound, but are otherwise invisible. Add a command
to show what callbacks are available.
Signed-off-by: Joe Hershberger
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
README | 1 +
common/cmd_nvedit.c | 77 +
Use a flag in hsearch_r for insert mode passed from import to allow the
behavior be different based on use.
Now that "do_check" is called for all imports, ensure console init is
complete before updating the console on relocation import
Signed-off-by: Joe Hershberger
---
Changes in v4:
- Prevent
Move the getenv_yesno() to env_common.c and change most checks for
'y' or 'n' to use this helper.
Signed-off-by: Joe Hershberger
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
arch/arm/lib/board.c| 4 +---
arch/m68k/lib/board.c | 3 +--
arch/microblaze/l
When printing all variables with env print, don't print variables that
begin with '.'. If env print is called with a '-a' switch, then
include variables that begin with '.' (just like the ls command).
Variables printed explicitly will be printed even without the -a.
Signed-off-by: Joe Hershberge
Remove the hard-coded loadaddr handler and use a callback instead
Signed-off-by: Joe Hershberger
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
common/cmd_nvedit.c| 12
common/image.c | 21 +
include/env_callback.h | 1 +
3 files ch
Remove the hard-coded bootfile handler and use a callback instead
Signed-off-by: Joe Hershberger
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
common/cmd_nvedit.c| 9 -
include/env_callback.h | 1 +
net/net.c | 17 +
3 files changed,
Similar to the env callback command, this will show details about the
options available, the static list, and the currently active variables.
Signed-off-by: Joe Hershberger
---
Changes in v4:
- Add help text for env flags command
Changes in v3: None
Changes in v2: None
README | 1
isspace() and strim() are not in the typical user-mode string.h, so
put them in a separate compilation unit so that they can be built into
tools that need them independent of the other common string functions.
This allows code shared by u-boot and the linux user-mode tools to link.
Signed-off-by:
Now that we have support for permissions, add a way to override them.
Signed-off-by: Joe Hershberger
---
Changes in v4:
- Add force support to setenv
Changes in v3: None
Changes in v2: None
common/cmd_nvedit.c | 29 +++--
1 file changed, 23 insertions(+), 6 deletions(-)
The same chunk of code was replicated in two places and the following
changes will make that chunk grow a bit, so combine into a static func.
Signed-off-by: Joe Hershberger
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
lib/hashtable.c | 71 ++---
The silent variable now updates the global data flag anytime it is
changed as well as after the env relocation (in case its value is
different from the default env in such cases as NAND env)
Signed-off-by: Joe Hershberger
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
common/co
Add support for per-variable callbacks to the "hashtable" functions.
Signed-off-by: Joe Hershberger
---
Changes in v4: None
Changes in v3:
- Use Marek's linker lists instead of implementing it directly
- Rebase onto latest master
- Add flags parameter to callbacks
- Implement reverse search in en
Currently just validates variable types as decimal, hexidecimal,
boolean, ip address, and mac address. Call
env_acl_validate_setenv_params() from setenv() in fw_env.c.
If the entry is not found in the env .flags, then look in the static
one. This allows the env to override the static definitions,
Add support for read-only, write-once, and change-default.
Signed-off-by: Joe Hershberger
---
Changes in v4: None
Changes in v3: None
Changes in v2: None
README| 13 -
common/cmd_nvedit.c | 31 --
common/env_common.c | 18 ++
common/env_flags.c| 153 ++
Hi Joe,
What a series! I haven't had a really good look, so I'm having a bit
of trouble getting my head around it all, but this looks very
impressive. I'm almost sorry for the nit I'm about to make...
On Wed, Dec 5, 2012 at 12:52 PM, Joe Hershberger wrote:
> Add support for per-variable callback
68 matches
Mail list logo