When the nand is first probe, and upon the first command start, the
status bits should be cleared before the interrupts are unmasked.
Cc: Robert Jarzmik
Signed-off-by: Chris Packham
---
drivers/mtd/nand/pxa3xx_nand.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers
When 2 commands are submitted in a row, and the second is very quick,
the completion of the second command might never come. This happens
especially if the second command is quick, such as a status read
after an erase
Cc: Robert Jarzmik
Signed-off-by: Chris Packham
---
drivers/mtd/nand
should be read/written for the
current read/program step.
- Reworks the state machine to accommodate doing the additional read
or program step when a last partial chunk is used.
Cc: Thomas Petazzoni
Signed-off-by: Chris Packham
---
drivers/mtd/nand/pxa3xx_nand.c | 154 +++
On Fri, Oct 21, 2016 at 1:58 AM, Ezequiel Garcia
wrote:
> On 20 October 2016 at 01:31, Chris Packham wrote:
>> The initial buffer is used for the initial commands used to detect
>> a flash device (STATUS, READID and PARAM).
>>
>> ONFI param page is 256 bytes, and there
Signed-off-by: Chris Packham
---
I'm keen to see this for the 88f6820-amc at least but I did wonder if it
should be enabled for more of the mvebu boards? Marvell don't really
make use of FIT images in their SDKs but I personally find them
incredibly useful. It adds about 32KiB to the f
Prevent cache misalignment message by ensuring that a whole cache line
is flushed.
Signed-off-by: Chris Packham
---
cmd/load.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/cmd/load.c b/cmd/load.c
index 65557e4f9ec3..77c3359b29b7 100644
--- a/cmd/load.c
+++ b/cmd/load.c
The main PLL frequency is 2GHz for Armada-XP and 1GHZ for Armada 375,
38x and 39x.
[ Linux commit ae142bd9976532aa5232ab0b00e621690d8bfe6a ]
Signed-off-by: Chris Packham
---
See
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ae142bd99765
I've set the valu
should be at least
512 x 3. This commits rounds the buffer size to 2048.
[ Linux commit c16340973fcb6461474a9f811f7f3ff2f946b24c ]
Cc: Ezequiel Garcia
Signed-off-by: Chris Packham
---
Changes in v2:
- Add reference to Linux commit sha1.
- Remove spurious change
drivers/mtd/nand/pxa3xx_nand.c | 15
nux commit sha1.
- Remove spurious change in 1/10
- Drop irrelevant Cc from 2/10
- 6/10 to 9/10 are new
Chris Packham (10):
mtd: nand: pxa3xx_nand: Increase initial buffer size
mtd: nand: pxa3xx_nand: use nand_to_mtd()
mtd: nand: pxa3xx_nand: sync pxa3xx_nand_set_sdr_timing()
mtd: nand: pxa3xx
Since the pxa3xx_nand driver was added there has been a discrepancy in
pxa3xx_nand_set_sdr_timing() around the setting of tWP_min and tRP_min.
This brings us into line with the current Linux code.
Signed-off-by: Chris Packham
---
Changes in v2:
- None
drivers/mtd/nand/pxa3xx_nand.c | 4
Don't store struct mtd_info in struct pxa3xx_nand_host. Instead use the
one that is already part of struct nand_chip. This brings us in line
with current U-boot and Linux conventions.
Signed-off-by: Chris Packham
---
Changes in v2:
- Drop irrelevant Cc from commit message
drivers/mtd
2 KiB, page size: 4096, OOB size: 224
[ Linux commit c7f00c29aa846b00c70bc99ddb6b1cc7e17c47d4 ]
Cc: Ezequiel García
Signed-off-by: Chris Packham
---
Changes in v2:
- new patch
drivers/mtd/nand/pxa3xx_nand.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mtd
Signed-off-by: Chris Packham
---
Changes in v2:
- Add reference to Linux commit sha1
drivers/mtd/nand/pxa3xx_nand.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/drivers/mtd/nand/pxa3xx_nand.c b/drivers/mtd/nand/pxa3xx_nand.c
index 4cd1297e1d59..c97d85782cb1
When the nand is first probe, and upon the first command start, the
status bits should be cleared before the interrupts are unmasked.
[ Linux commit 0b14392db2e998157d924085d7913e537ec26121 ]
Cc: Robert Jarzmik
Signed-off-by: Chris Packham
---
Changes in v2:
- Add reference to Linux commit
efore nand_scan_ident()
and the second group later.
Let's split pxa3xx_nand_config in two halves, and set the
parameters that depend on the device geometry once this is known.
[ Linux commit 66e8e47eae658dc884e65695a597fdda7a109448 ]
Cc: Ezequiel Garcia
Signed-off-by: Chris Packham
---
Changes in
ommit b226eca2088004622434cbcc27c6401b64f22d7c]
Cc: Ezequiel García
Signed-off-by: Chris Packham
---
Changes in v2:
- New
drivers/mtd/nand/pxa3xx_nand.c | 29 ++---
1 file changed, 10 insertions(+), 19 deletions(-)
diff --git a/drivers/mtd/nand/pxa3xx_nand.c b/drivers/mtd
This commit simplifies the initial configuration performed
by pxa3xx_nand_scan. No functionality change is intended.
[ Linux commit 154f50fbde539c20bbf74854461d932ebdace4d5 ]
Cc: Ezequiel García
Signed-off-by: Chris Packham
---
Changes in v2:
- New
drivers/mtd/nand/pxa3xx_nand.c | 30
should be read/written for the
current read/program step.
- Reworks the state machine to accommodate doing the additional read
or program step when a last partial chunk is used.
[ Linux commit c2cdace755b583bae540a9979bff1aa428181b8c ]
Cc: Thomas Petazzoni
Signed-off-by: Chris Packham
---
C
Hi,
Is there a standard way of passing information discovered by the SPL
onto the next boot stage?
I'm guessing for platforms that support the new driver model it's
possible to add/update information in the device-tree, but what about
platforms that don't currently use the new driver model.
I ha
On Tue, Jul 26, 2016 at 2:51 AM, Tom Rini wrote:
> On Mon, Jul 25, 2016 at 08:54:27PM +1200, Chris Packham wrote:
>
>> Hi,
>>
>> Is there a standard way of passing information discovered by the SPL
>> onto the next boot stage?
>>
>> I'm guessing
On Tue, Jul 26, 2016 at 11:51 AM, Chris Packham wrote:
> On Tue, Jul 26, 2016 at 2:51 AM, Tom Rini wrote:
>> On Mon, Jul 25, 2016 at 08:54:27PM +1200, Chris Packham wrote:
>>
>>> Hi,
>>>
>>> Is there a standard way of passing information discover
From: Chris Packham
Add pin control settings for the NAND flash interface. This interface
is multiplexed with the device bus interface to the function is "dev"
not "nand" as one might expect.
Signed-off-by: Chris Packham
Cc: Luka Perkov
Cc: Dirk Eibach
---
I don'
From: Chris Packham
The NAND interface on the Armada-38x series is similar to that on the
Armada-XP. The key difference is that the NAND ECC clock ratio is
provided via the DFX Server registers instead of the Core Clock.
Signed-off-by: Chris Packham
Cc: Luka Perkov
Cc: Dirk Eibach
---
I
As of commit 88e34e5 ("spl: replace CONFIG_SPL_SPI_* with
CONFIG_SF_DEFAULT_*") these defines are not used. Remove them to avoid
confusion.
Signed-off-by: Chris Packham
---
I decided to go with a single patch as with the exception of ds414 these
all appear to be Armada based boards. I
Ensure appropriate error messages are generated. Previously all errors
indicated that the serdes was already in use. Now appropriate error
messages are given.
Signed-off-by: Chris Packham
---
This looks to be a misplaced brace. Effectively the error handling for
UNIT_NUMBER_VIOLATION and
Signed-off-by: Chris Packham
---
arch/arm/mach-mvebu/serdes/a38x/ctrl_pex.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-mvebu/serdes/a38x/ctrl_pex.c
b/arch/arm/mach-mvebu/serdes/a38x/ctrl_pex.c
index 06a7715..98c447c 100644
--- a/arch/arm/mach-mvebu/serdes
On Tue, Aug 23, 2016 at 6:57 PM, Stefan Roese wrote:
> Hi Chris,
>
> On 22.08.2016 02:38, Chris Packham wrote:
>>
>> From: Chris Packham
>>
>> Add pin control settings for the NAND flash interface. This interface
>> is multiplexed with the device bus in
Hi Stefan,
On Tue, Aug 23, 2016 at 10:54 PM, Chris Packham wrote:
> On Tue, Aug 23, 2016 at 6:57 PM, Stefan Roese wrote:
>> Hi Chris,
>>
>> On 22.08.2016 02:38, Chris Packham wrote:
>>>
>>> From: Chris Packham
>>>
>>> Add pin control set
passed to
mv88e61xx_port_set_vlan().
Other than that it's just a matter of adding the appropriate chip
IDs.
Signed-off-by: Chris Packham
Cc: Joshua Scott
---
This is a re-work of Joshua's patch
http://patchwork.ozlabs.org/patch/425556/
Thanks to the work from Kevin Smith the changes
On some boards these switches are wired directly into a SERDES
interface on another Ethernet MAC. Add the ability to specify
these kinds of boards using CONFIG_MV88E61XX_FIXED_PORTS which defines
a bit mask of these fixed ports.
Signed-off-by: Chris Packham
---
drivers/net/phy/mv88e61xx.c | 43
In commit 17cb4b8f327e ("mtd: nand: Add+use mtd_to/from_nand and
nand_get/set_controller_data") the assignment of mtd->priv was removed
but was not replaced. This adds the required nand_set_controller_data()
call.
Signed-off-by: Chris Packham
---
drivers/mtd/nand/pxa3xx_nand.c
Hi,
I'm updating support for a board which uses the Armada-385 from u-boot
v2016.05 to use the latest master (v2016.09-rc2 plus a bit).
When I run "sf probe" I get a divide by 0 in mvebu_spi_set_speed
because hz has made it through as 0.
When I run saveenv (env is in SPI) I don't get the divide
On Mon, Aug 29, 2016 at 5:55 PM, Stefan Roese wrote:
> Hi Chris,
>
> (added Tom to Cc)
>
> On 29.08.2016 07:49, Chris Packham wrote:
>>
>> I'm updating support for a board which uses the Armada-385 from u-boot
>> v2016.05 to use the latest master (v2016.09
Signed-off-by: Chris Packham
---
drivers/net/mvneta.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/mvneta.c b/drivers/net/mvneta.c
index c23fe9a9d5a7..bbfce9604710 100644
--- a/drivers/net/mvneta.c
+++ b/drivers/net/mvneta.c
@@ -1589,7 +1589,7 @@ static int
On Tue, Aug 30, 2016 at 12:52 AM, Jagan Teki wrote:
> On Mon, Aug 29, 2016 at 1:34 PM, Chris Packham
> wrote:
>> On Mon, Aug 29, 2016 at 5:55 PM, Stefan Roese wrote:
>>> Hi Chris,
>>>
>>> (added Tom to Cc)
>>>
>>> On 29.08.2016 07:49,
On Tue, Aug 30, 2016 at 10:19 PM, John Rama wrote:
> Dear u-boot network experts,
>
> I'm now working on NXP MX6Q Sabreauto board with AR8031 network card.
> I'm using rel_imx_4.1.15_1.2.0_ga.
>
> Basically, the network works fine. u-boot can send ping to other device, do
> the tftp boot as well.
On Wed, Aug 31, 2016 at 11:24 PM, Robert P. J. Day
wrote:
>
> just tripped across this in master branch:
>
> $ grep -rw CONFIG_RAMBOOT *
> doc/README.ramboot-ppc85xx: #ifdef CONFIG_RAMBOOT
> include/configs/at91rm9200ek.h:#ifdef CONFIG_RAMBOOT
> README: CONFIG_RAMBOOT and CONFIG_NFSBOO
On Mon, Aug 29, 2016 at 3:20 PM, Chris Packham wrote:
> In commit 17cb4b8f327e ("mtd: nand: Add+use mtd_to/from_nand and
> nand_get/set_controller_data") the assignment of mtd->priv was removed
> but was not replaced. This adds the required nand_set_controller_data()
>
This board is a plug in card for Marvell's switch system development
kits. Form-factor aside it is similar to the DB-88F6820-GP with the
following differences.
- TCLK is 200MHz
- SPI1 is used
- No SATA
- No MMC
- NAND flash
Signed-off-by: Chris Packham
---
I've used my work email addre
88F6820 is a specific Armada-38x chip that is used on the DB-88F6820-GP
board. Rather than having DB_88F6820_GP and TARGET_DB_88F6820_GP which
selects the former. Rename DB_88F6820_GP to 88F6820 so that other boards
using the 88F6820 can be added.
Signed-off-by: Chris Packham
---
arch/arm/mach
Enable the NAND interface on this board.
Signed-off-by: Chris Packham
---
arch/arm/dts/armada-385-amc.dts | 8
configs/db-88f6820-amc_defconfig | 2 ++
include/configs/db-88f6820-amc.h | 4
3 files changed, 14 insertions(+)
diff --git a/arch/arm/dts/armada-385-amc.dts b/arch
On Mon, Sep 19, 2016 at 12:58 PM, Simon Glass wrote:
> Hi Chris,
>
> On 13 September 2016 at 19:42, Chris Packham wrote:
>> This board is a plug in card for Marvell's switch system development
>> kits. Form-factor aside it is similar to the DB-88F6820-GP with th
This board is a plug in card for Marvell's switch system development
kits. Form-factor aside it is similar to the DB-88F6820-GP with the
following differences.
- TCLK is 200MHz
- SPI1 is used
- No SATA
- No MMC
- NAND flash
Reviewed-by: Simon Glass
Signed-off-by: Chris Packham
---
I'
88F6820 is a specific Armada-38x chip that is used on the DB-88F6820-GP
board. Rather than having DB_88F6820_GP and TARGET_DB_88F6820_GP which
selects the former. Rename DB_88F6820_GP to 88F6820 so that other boards
using the 88F6820 can be added.
Signed-off-by: Chris Packham
---
Changes in v2
Enable the NAND interface on this board.
Signed-off-by: Chris Packham
---
Changes in v2: None
arch/arm/dts/armada-385-amc.dts | 8
configs/db-88f6820-amc_defconfig | 2 ++
include/configs/db-88f6820-amc.h | 4
3 files changed, 14 insertions(+)
diff --git a/arch/arm/dts/armada
console_update_silent() and call it from both
console_init_f() and console_init_r().
Signed-off-by: Chris Packham
---
common/console.c | 17 +
1 file changed, 13 insertions(+), 4 deletions(-)
diff --git a/common/console.c b/common/console.c
index 12293f383624..c7f32434310e 100644
--- a/common
Hi,
I'm working with a new board using u-boot v2016.11. The board is using
a SoC (Marvell integrated switch using armada-xp "compatible" core).
While the SoC does have some built-in Ethernet interfaces the board I
have only has USB available.
Based on doc/README.usb I expect that running "usb sta
On 29/01/2017 8:51 AM, "Tom Rini" wrote:
On Wed, Jan 25, 2017 at 10:56:20PM +1300, Chris Packham wrote:
> Signed-off-by: Chris Packham
> ---
>
> Changes in v3:
> - Add brief testing section
[snip]
> +Testing using QEMU
> +--
> +Refer to README.
When gathering addresses for the Cc list patman would encounter a
UnicodeDecodeError due to non-ascii characters in the author name.
Address this by explicitly using utf-8 when building the Cc list.
Signed-off-by: Chris Packham
---
On Tue, Feb 7, 2017 at 4:32 AM, Simon Glass wrote:
> Hi Ch
Hi,
I just tried UART booting db-88f6820-amc with the latest u-boot master
and it fails to reach the normal u-boot prompt. I don't know if this
affects the normal SPI booting.
I've bisected down to commit 94084eea3bd3 ("tools: kwbimage: Fix dest addr").
Reverting this gets things working again,
On Tue, Feb 14, 2017 at 7:56 PM, Mario Six wrote:
> On Tue, Feb 14, 2017 at 7:36 AM, Stefan Roese wrote:
>> Hi Chris,
>>
>> On 14.02.2017 02:48, Chris Packham wrote:
>>>
>>> I just tried UART booting db-88f6820-amc with the latest u-boot master
>>>
On Tue, Feb 14, 2017 at 11:01 PM, Mario Six wrote:
> On Tue, Feb 14, 2017 at 10:26 AM, Chris Packham
> wrote:
>> On Tue, Feb 14, 2017 at 7:56 PM, Mario Six wrote:
>>> On Tue, Feb 14, 2017 at 7:36 AM, Stefan Roese wrote:
>>>> Hi Chris,
>>>>
On Wed, Feb 15, 2017 at 11:56 AM, Chris Packham wrote:
> On Tue, Feb 14, 2017 at 11:01 PM, Mario Six wrote:
>> On Tue, Feb 14, 2017 at 10:26 AM, Chris Packham
>> wrote:
>>> On Tue, Feb 14, 2017 at 7:56 PM, Mario Six wrote:
>>>> On Tue, Feb 14, 2017 at 7:
On Wed, Feb 15, 2017 at 11:56 AM, Chris Packham wrote:
> On Tue, Feb 14, 2017 at 11:01 PM, Mario Six wrote:
>> On Tue, Feb 14, 2017 at 10:26 AM, Chris Packham
>> wrote:
>>> On Tue, Feb 14, 2017 at 7:56 PM, Mario Six wrote:
>>>> On Tue, Feb 14, 2017 at 7:
Commit 94084eea3bd3 ("tools: kwbimage: Fix dest addr") changed kwbimage
to do this adjustment. So now the adjustment in kwboot is not needed
(and would prevent UART booting for images generated by the new
kwbimage). Remove the destaddr adjustment in kwboot.
Signed-off-by: Chr
e I really want to see. As it allows me to
switch a board I'm working on over to the driver model. I've tried to
replicate the non-DM version of the driver faithfully but I've only got
access to a ds1340 device so I can't be sure that the mcp7941x specific
code is correct.
Ch
Signed-off-by: Chris Packham
---
cmd/Kconfig | 6 ++
1 file changed, 6 insertions(+)
diff --git a/cmd/Kconfig b/cmd/Kconfig
index 13dc46a..1aaf8c5 100644
--- a/cmd/Kconfig
+++ b/cmd/Kconfig
@@ -676,6 +676,12 @@ config CMD_LED
with led on/off/togle/blink. Any LED drivers can be
Add an implementation of the ds1307 driver that uses the driver model
i2c APIs.
Signed-off-by: Chris Packham
---
drivers/rtc/Kconfig | 7 ++
drivers/rtc/ds1307.c | 196 ++-
2 files changed, 184 insertions(+), 19 deletions(-)
diff --git a
Add an implementation of the ds1307 driver that uses the driver model
i2c APIs.
Signed-off-by: Chris Packham
---
Changes in v2: None
drivers/rtc/Kconfig | 7 ++
drivers/rtc/ds1307.c | 196 ++-
2 files changed, 184 insertions(+), 19 deletions
only got
access to a ds1340 device so I can't be sure that the mcp7941x specific
code is correct.
Changes in v2:
- run moveconfig.py
Chris Packham (2):
cmd: add Kconfig option for 'date' command
rtc: Add DM support to ds1307
cmd/Kconfig
(drop long Cc list to stop mailman complaining)
On Thu, Apr 27, 2017 at 5:22 AM, Simon Glass wrote:
> On 25 April 2017 at 23:19, Chris Packham wrote:
>>
>> Signed-off-by: Chris Packham
>>
>> ---
>> As requested I've run moveconfig.py to update the de
On Thu, Apr 27, 2017 at 8:24 AM, Tom Rini wrote:
> On Thu, Apr 27, 2017 at 05:55:18AM +1200, Chris Packham wrote:
>> (drop long Cc list to stop mailman complaining)
>>
>> On Thu, Apr 27, 2017 at 5:22 AM, Simon Glass wrote:
>> > On 25 April 2017 at 23:19, Chris Pack
In preparation for the next change that adds a new option.
Signed-off-by: Chris Packham
---
This isn't strictly needed. I did this so the next patch only touched
CONFIG_CMD_DATE and I figured I may as well send this out so it can be
applied if desired.
Changes in v3: None
Changes in v2:
Add an implementation of the ds1307 driver that uses the driver model
i2c APIs.
Signed-off-by: Chris Packham
---
Changes in v3: None
Changes in v2: None
drivers/rtc/Kconfig | 7 ++
drivers/rtc/ds1307.c | 196 ++-
2 files changed, 184
move CONFIG_CMD_DATE from whitelist
Changes in v2:
- run moveconfig.py
Chris Packham (3):
configs: sync P101x, P102x, P202x defconfgs
cmd: add Kconfig option for 'date' command
rtc: Add DM support to ds1307
cmd/Kconfig| 6 +
configs/B4420QDS_NAND
Hi Simon,
On Thu, Apr 27, 2017 at 4:27 PM, Simon Glass wrote:
> This converts the following to Kconfig:
>CONFIG_CMD_AES
>CONFIG_AES
>
> Signed-off-by: Simon Glass
> ---
>
> cmd/Kconfig | 9 +
> configs/seaboard_defconfig| 1 +
> include/configs/amcore.h
After moving to KConfig and removing from all headers options should be
removed from config_whitelist.txt so the build starts complaining if
someone adds them back.
Signed-off-by: Chris Packham
---
Simon asked for it so here you go. I also thought about cleaning up the
README file references too
After moving to KConfig and removing from all headers options should be
removed from config_whitelist.txt so the build starts complaining if
someone adds them back.
Acked-by: Masahiro Yamada
Signed-off-by: Chris Packham
---
Simon asked for it so here you go. I also thought about cleaning up the
On Sat, Apr 29, 2017 at 12:27 PM, Simon Glass wrote:
> Hi Chris,
>
> On 25 April 2017 at 23:19, Chris Packham wrote:
>> Add an implementation of the ds1307 driver that uses the driver model
>> i2c APIs.
>>
>> Signed-off-by: Chris Packham
>>
>> ---
In preparation for the next change that adds a new option.
Signed-off-by: Chris Packham
---
This isn't strictly needed. I did this so the next patch only touched
CONFIG_CMD_DATE and I figured I may as well send this out so it can be
applied if desired.
Changes in v4: None
Changes in v3:
Add an implementation of the ds1307 driver that uses the driver model
i2c APIs.
Signed-off-by: Chris Packham
---
Changes in v4:
- move #ifdef CONFIG_CMD_DATE inside the legacy block
- use driver data to identify specific chip
- terminate the #ifndef with a #endif rather than having backwards
ist
Changes in v2:
- run moveconfig.py
Chris Packham (3):
configs: sync P101x, P102x, P202x defconfgs
cmd: add Kconfig option for 'date' command
rtc: Add DM support to ds1307
cmd/Kconfig| 6 +
configs/B4420QDS_NAND_defconfig
There is some inconsistency between uses of CONFIG_RTC_DS13xx and
CONFIG_SYS_RTC_DS13xx. Address this by dropping the "SYS" from
these variables.
Signed-off-by: Chris Packham
---
README | 2 +-
drivers/rtc/ds1337.c | 16
include/configs
On Sat, Mar 12, 2016 at 9:18 AM, Scott Wood wrote:
> On Fri, 2016-03-11 at 12:13 -0800, Steve Rae wrote:
>> On Fri, Mar 11, 2016 at 11:55 AM, Scott Wood wrote:
>> > On Fri, 2016-03-11 at 11:47 -0800, Steve Rae wrote:
>> > > On Fri, Mar 11, 2016 at 11:29 AM, Scott Wood wrote:
>> > > > On Thu, 201
(trying newer address for Steve, sorry for the spam)
> On Sat, Mar 12, 2016 at 9:18 AM, Scott Wood wrote:
>> On Fri, 2016-03-11 at 12:13 -0800, Steve Rae wrote:
>>> On Fri, Mar 11, 2016 at 11:55 AM, Scott Wood wrote:
>>> > On Fri, 2016-03-11 at 11:47 -0800, Steve Rae wrote:
>>> > > On Fri, Mar 1
Hi Duncan,
On Tue, Jun 6, 2017 at 1:01 PM, Duncan Hare wrote:
> U-boot support DHCP, however beyond the initial set of results returned, many
> are optional, and even misused.
>
> Microsoft's DHCP server appears to have a limited mechanism to set DHCP
> responses.
>
> Because u-boot runs on "sm
On Sun, Apr 30, 2017 at 3:49 PM, Simon Glass wrote:
> On 28 April 2017 at 21:20, Chris Packham wrote:
>> Add an implementation of the ds1307 driver that uses the driver model
>> i2c APIs.
>>
>> Signed-off-by: Chris Packham
>>
>> ---
>>
>> Cha
On Tue, May 2, 2017 at 3:15 AM, York Sun wrote:
> On 04/28/2017 08:20 PM, Chris Packham wrote:
>>
>> In preparation for the next change that adds a new option.
>>
>> Signed-off-by: Chris Packham
>>
>> ---
>> This isn't strictly needed. I did this
Move existing configuration from header file to defconfig or dts as
appropriate.
Signed-off-by: Chris Packham
---
arch/arm/dts/armada-385-amc.dts | 3 +++
configs/db-88f6820-amc_defconfig | 2 ++
include/configs/db-88f6820-amc.h | 7 ---
3 files changed, 5 insertions(+), 7 deletions
Avoid repetitive code dealing with asking the user for confirmation.
Signed-off-by: Chris Packham
---
Changes in v3: None
Changes in v2: None
tools/moveconfig.py | 37 ++---
1 file changed, 18 insertions(+), 19 deletions(-)
diff --git a/tools/moveconfig.py b
After moving to KConfig and removing from all headers options should be
removed from config_whitelist.txt so the build starts complaining if
someone adds them back.
Acked-by: Masahiro Yamada
Signed-off-by: Chris Packham
---
Simon asked for it so here you go. I also thought about cleaning up the
CONFIG_CMD_DATE was recently moved to Kconfig. Remove the now duplicate
description of the option.
Signed-off-by: Chris Packham
---
Changes in v3: None
Changes in v2: None
README | 1 -
1 file changed, 1 deletion(-)
diff --git a/README b/README
index 0ac0136..78173e2 100644
--- a/README
The Kconfig description replaces the description in the README file so
as options are migrated they can be removed from the README.
Signed-off-by: Chris Packham
---
Changes in v3: None
Changes in v2: None
tools/moveconfig.py | 41 +
1 file changed, 41
Hi
On 6/05/2017 3:57 PM, "Kernel Hacker" wrote:
On 04/25/2017 09:04 PM, Kernel Hacker wrote:
> I have a Guruplug server standard that I would like to upgrade with a
> newer version of u-boot. Serial output during boot currently shows the
> following:
>
> cut
>
>
On 9/05/2017 2:13 PM, "Tom Rini" wrote:
The variable 'res' may be unused uninitialized if our call to
mv88e61xx_port_read (register read) fails and we goto the error
handling section. In this case we set 'res' to -EIO to indicate why we
failed.
Cc: Joe Hershberger
On Fri, May 12, 2017 at 9:53 PM, Vic wrote:
> Hi All.
>
> I'm having difficulty with getting a board booting Linux from U-boot. This
> is an existing unit, so I don't get much choice over changing versions of
> kernel of U-boot.
>
> bdinfo gives me the machine ID I expect, but when I try to boot m
On 15/05/2017 11:47 PM, "Simon Glass" wrote:
Add a -b option which scans all the defconfigs and builds a database of
all the CONFIG options used by each. This is useful for querying later.
At present this only works with the separate -b option, which does not
move any configs. It would be possib
Some network devices/drivers need to insert special tags in packets as
they are transmitted (e.g. Marvell's DSA tag for their switch devices).
Add an option to leave a little space at the start of the packets
Reviewed-by: Mark Tomlinson
Signed-off-by: Chris Packham
---
This is analogo
Claim the MPP pins for the NAND flash controller only when it's actually
being used. This allows the pins to be shared with the SPI interface
which already supports an equivalent on-access MPP reconfiguration.
Reviewed-by: Mark Tomlinson
Signed-off-by: Chris Packham
---
I haven't wr
Hi,
Is there any hook for performing board specific actions prior to
booting the OS. A quick google search turned up this thread from
2014[1]. But the eventual outcome seemed to be that the device model
will take care of restoring devices to their unused state, for
anything else there is arch_preb
Hi Scott,
On Sat, Jan 23, 2016 at 9:11 AM, Scott Wood wrote:
> On Fri, 2016-01-15 at 17:22 +1300, Chris Packham wrote:
>> Claim the MPP pins for the NAND flash controller only when it's actually
>> being used. This allows the pins to be shared with the SPI interface
>>
Set the appropriate bits in the interface config register based
on the SPI_ mode flags.
Signed-off-by: Chris Packham
---
Changes in v2:
- Clear bits before updating
arch/arm/include/asm/arch-mvebu/spi.h | 4
drivers/spi/kirkwood_spi.c| 15 +++
2 files changed, 19
On 27/10/2016 10:41 PM, "Jagan Teki" wrote:
>
> On Thu, Oct 27, 2016 at 1:46 PM, Chris Packham
wrote:
> > Set the appropriate bits in the interface config register based
> > on the SPI_ mode flags.
> >
> > Signed-off-by: Chris Packham
>
> Missed upd
in that
commit build errors where triggered when CONFIG_PHYLIB was enabled.
Fix these build errors by removing mvgbe_phy_read and mvgbe_phy_write
and using smi_reg_read/smi_reg_write directly.
Signed-off-by: Chris Packham
---
Looking at this closer it actually appears that the mvgbe driver has 2
Offset 0x18 in some Marvell datasheets this field is redacted as
"reserved". This offset is actually a set of options and bits 2:0 allow
the selection of the UART baudrate.
Allow a BAUDRATE option to set the UART baudrate for any messages coming
from the BootROM firmware.
Signed-off
Offset 0x1 in the generated kwb image file is a set of flags, bit 0
enables debug output from the BootROM firmware. Allow a DEBUG option in
the kwb configuration to request debug output from the BootROM firmware.
Signed-off-by: Chris Packham
---
tools/kwbimage.c | 9 +
tools
Prepare for move to Kconfig by removing "SYS" from the existing macros.
Signed-off-by: Chris Packham
---
README | 2 +-
board/astro/mcf5373l/fpga.c | 4 ++--
drivers/fpga/ACEX1K.c| 8
drivers/fpga/cyclon2.c
nt to introduce.
We have some boards where the FPGA images require the reverse bitstream
mode. I think this may be some setting in the Xilinx tools but it seems
to be permanently set in the images coming out of our hardware team.
Chris Packham (7):
fpga: CONFIG_SYS_FPGA_PROG_FEE
Signed-off-by: Chris Packham
---
configs/apf27_defconfig | 1 +
configs/astro_mcf5373l_defconfig | 1 +
configs/mt_ventoux_defconfig | 1 +
include/configs/apf27.h | 1 -
include/configs/astro_mcf5373l.h | 1 -
include/configs/mt_ventoux.h | 2 --
6 files changed, 3
Signed-off-by: Chris Packham
---
drivers/fpga/Kconfig | 11 +++
1 file changed, 11 insertions(+)
diff --git a/drivers/fpga/Kconfig b/drivers/fpga/Kconfig
index f3f6bf7f6747..d137ab2df1d7 100644
--- a/drivers/fpga/Kconfig
+++ b/drivers/fpga/Kconfig
@@ -17,4 +17,15 @@ config
601 - 700 of 1096 matches
Mail list logo