Hi,
Is there any chance for this patch to be upstreamed in the next release ?
On sheevaplug if you try the latest u-boot you may be brick the plug.
It will be corrupted because of the size of the of the u-boot binary.
The fix of env location proposed is a needed fix.
I have still some few patch
There is no good reason to keep this code separate. Move it into control.py
so it is easier to test.
Signed-off-by: Simon Glass
---
Changes in v3: None
Changes in v2: None
tools/buildman/buildman.py | 6 --
tools/buildman/control.py | 8
2 files changed, 8 insertions(+), 6 deleti
Tags like Series-version are normally expected to appear once, and with a
unique value. But buildman doesn't actually look at these tags. So ignore
conflicts.
This allows bulidman to build a branch containing multiple patman series.
Reported-by: Steve Rae
Signed-off-by: Simon Glass
---
Changes
Rather than reading boards.cfg, which may take time to generate and is not
necessarily suitable for running tests, create our own list of boards.
Signed-off-by: Simon Glass
---
Changes in v3: None
Changes in v2: None
tools/buildman/control.py | 21 -
tools/buildman/func_t
Adjust the basic test so that it checks all console output. This will help
to ensure that the builder is behaving correctly with printing summary
information.
Signed-off-by: Simon Glass
---
Changes in v3: None
Changes in v2: None
tools/buildman/test.py | 101 +++
When running unit tests we don't want output to go to the terminal.
Provide a way of collecting it so that it can be examined by test code
later.
Signed-off-by: Simon Glass
---
Changes in v3: None
Changes in v2:
- Add a function to print out the terminal output recorded
tools/patman/terminal.p
Buildman currently lacks testing in many areas, including its use of git,
make and many command-line flags.
Add a functional test which covers some of these areas. So far it does
a fake 'build' of all boards for the current source tree.
This version reads the real ~/.buildman and boards.cfg files
At present buildman naively uses the branch name as part of its directory
path, which causes problems if the name has an embedded '/'.
Replace these with '_' to fix the problem.
Reported-by: Steve Rae
Signed-off-by: Simon Glass
---
Changes in v3:
- Add new patch to permit branch names with an
For reasons that are not well-understood, GetMetaDataForList() can end up
adding to an existing series even when it appears that it should be
starting a new one.
Change from using a default constructor parameter to an explicit one, to
work around this problem.
Signed-off-by: Simon Glass
---
Cha
Now that buildman supports removing the build directory prefix from output,
add a test for it. Also ensure that output directories are removed when the
test completes.
Signed-off-by: Simon Glass
---
Changes in v3: None
Changes in v2:
- Add patch to expand output test to cover directory prefixes
We want to be able to issue parser commands from within buildman for test
purposes. Move the parser code into its own file so we don't end up needing
the buildman and test modules to reference each other.
Signed-off-by: Simon Glass
---
Changes in v3: None
Changes in v2: None
tools/buildman/bui
For testing it is useful to clean the output directory before running a
test. This avoids a test interfering with the results of a subsequent
test by leaving data around.
Add this feature as an optional parameter to the control logic.
Signed-off-by: Simon Glass
---
Changes in v3: None
Changes i
These files may not exist in the environment, or may not be suitable for
testing. Provide our own config file and our own toolchains when running
tests.
Signed-off-by: Simon Glass
---
Changes in v3: None
Changes in v2: None
tools/buildman/bsettings.py | 15 ++-
tools/buildman/func_
When a build is to be performed, buildman checks to see if it has already
been done. In most cases it will not bother trying again. However, it was
not reading the return code from the 'done' file, so if the result was a
failure, it would not be counted. This depresses the 'failure' count stats
tha
This adds coverage of core features of the builder, including the
command-line options which affect building.
Signed-off-by: Simon Glass
---
Changes in v3: None
Changes in v2: None
tools/buildman/func_test.py | 324 +---
1 file changed, 306 insertions(+)
RunPipe() currently pipes the output of stdout and stderr to a pty, but
this is not the intended behaviour. Fix it.
Signed-off-by: Simon Glass
---
Changes in v3: None
Changes in v2: None
tools/patman/command.py | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tools/patman/command.py b/too
Move the bsettings code back to the main buildman.py file, so we can do
something different when testing.
Signed-off-by: Simon Glass
---
Changes in v3: None
Changes in v2: None
tools/buildman/buildman.py | 2 ++
tools/buildman/control.py | 1 -
2 files changed, 2 insertions(+), 1 deletion(-)
Add a test point for the command module. This allows tests to emulate
the execution of commands. This provides more control (since we can make
the fake 'commands' do whatever we like), makes it faster to write tests
since we don't need to set up as much environment, and speeds up test
execution.
S
To allow us to verify the builder's console output, send it through a
function which can collect it when running in test mode.
Signed-off-by: Simon Glass
---
Changes in v3: None
Changes in v2: None
tools/buildman/builder.py | 58 ---
1 file changed,
Hi Steve,
On 3 September 2014 18:34, Steve Rae wrote:
> example:
>
> $ tools/buildman/buildman -b dev/to_denx broadcom
> No section: 'make-flags'
> boards.cfg is up to date. Nothing to do.
> Building 1 commit for 4 boards (4 threads, 2 jobs per thread)
> Traceback (most recent call last):
> Fil
Buildman's test coverage is inadequate, particularly in the area of the
core builder threads and logic. As a result it is harder to make changes
than it should be, since verifying correctness manually is tedious.
The existing output test relies on the user to verify that things look
OK. This is ge
Hi,
On 6 May 2014 00:38, Heiko Schocher wrote:
> Hello Mike,
>
> Am 05.05.2014 16:27, schrieb Mike Pearce:
>>
>> Please help as I am confused.
>>
>> I implemented verified boot on 2014.04 using CONFIG_OF_SEPARATE and it
>> works fine with FIT images. However it still boots the resident legacy
>>
Hi Masahiro,
On 4 September 2014 20:55, Masahiro Yamada wrote:
> Hi Simon,
>
>
> On Wed, 3 Sep 2014 18:01:44 -0600
> Simon Glass wrote:
>
>> Hi Masahiro,
>>
>> On 31 August 2014 20:06, Masahiro Yamada wrote:
>> > We have not had a good method to debug the early boot stage such as
>> > lowlevel_
Hi,
On 3 September 2014 17:36, Simon Glass wrote:
> Now that driver model is part of U-Boot, the task of converting drivers over
> to it begins. GPIO is one of the easiest to convert, since it already has a
> sandbox driver and a uclass driver.
>
> The Tegra GPIO driver is relatively simple since
Hi,
On 4 September 2014 16:27, Simon Glass wrote:
> This series adds support for a serial uclass, enabling serial drivers to be
> converted to use driver model.
>
> With v4, exynos boards all build and a second attempt has been made to add
> Tegra support via the ns16550 driver, tested on beaver,
From: Hao Zhang
This patches enables the On-chip Shared Ram clock domain for K2L SoC.
Signed-off-by: Hao Zhang
Signed-off-by: Ivan Khoronzhuk
---
arch/arm/cpu/armv7/keystone/init.c| 49 +++
arch/arm/include/asm/arch-keystone/hardware-k2l.h | 25
From: Hao Zhang
This patch adds Keystone II Lamar (K2L) SoC specific definitions
to support MSMC cache coherency.
Acked-by: Vitaly Andrianov
Signed-off-by: Hao Zhang
Signed-off-by: Ivan Khoronzhuk
---
arch/arm/cpu/armv7/keystone/init.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/a
From: Hao Zhang
This patch adds Keystone II Lammar (K2L) EVM board support.
Acked-by: Vitaly Andrianov
Signed-off-by: Hao Zhang
Signed-off-by: Ivan Khoronzhuk
---
arch/arm/cpu/armv7/keystone/Kconfig| 3 ++
arch/arm/include/asm/arch-keystone/clock-k2l.h | 6 +++
board/ti/ks2_evm
From: Hao Zhang
This patch adds hardware definitions specific to Keystone II
Lamar (K2L) SoC.
Acked-by: Vitaly Andrianov
Signed-off-by: Hao Zhang
Signed-off-by: Ivan Khoronzhuk
---
arch/arm/include/asm/arch-keystone/hardware-k2hk.h | 2 -
arch/arm/include/asm/arch-keystone/hardware-k2l.h |
From: Hao Zhang
This patch adds clock definitions and commands to support Keystone II
K2L SOC.
Acked-by: Vitaly Andrianov
Signed-off-by: Hao Zhang
Signed-off-by: Ivan Khoronzhuk
---
arch/arm/cpu/armv7/keystone/Makefile | 1 +
arch/arm/cpu/armv7/keystone/clock-k2l.c| 138 +
From: Hao Zhang
Add Keystone II Lamar (K2L) SoC support.
Acked-by: Vitaly Andrianov
Signed-off-by: Hao Zhang
Signed-off-by: Ivan Khoronzhuk
---
arch/arm/cpu/armv7/keystone/spl.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/cpu/armv7/keystone/spl.c
b/arch/arm/cpu/armv7
This patch series adds Keystone II Lamar (K2L) SoC and k2l_evm
board support.
Based on
"[U-boot] [Patch v2] keystone: usb: add support of usb xhci"
https://patchwork.ozlabs.org/patch/386506/
v2..v1
Rebased according to changes of c338f09e965a300ddd78af73e86c4af4c9464ce4
"keystone:
Hi Tom,
This is the rest of the initial patman/buildman series, except for the
MAKEALL deprecation.
I plan to also pull in the second buildman/patman series (with its
fixes and new tests) for this release. There is a merge conflict with
one of Masahiro's changes, so I will either resolve this man
On 28 August 2014 09:21, Simon Glass wrote:
> This option is currently not supported, but needs to be, for buildman to
> operate as expected.
>
> Reported-by: York Sun
> Signed-off-by: Simon Glass
Applied to u-boot-x86/patman.
___
U-Boot mailing list
On Fri, Sep 5, 2014 at 3:36 PM, Fabio Estevam wrote:
> From: Fabio Estevam
>
> Commit fa9c021632473 ("mx6: add example DTB for mx6qsabreauto") introduced
> 'imx6q-sabreauto.dts' but it adds no real value as the dts file only contains
> the 'model' and 'compatible' strings.
>
> After this commit t
From: WingMan Kwok
Add support of usb xhci. xHCI controls all USB speeds of the Host
mode, that is, the SS through the SS PHY, as well as the HS, FS, and
LS through the USB2 PHY. xHCI replaces and supersedes all previous
host HCIs (HS-only EHCI, FS/LS OHCI and UHCI), and is therefore not
backward
On Fri, Sep 05, 2014 at 12:08:13PM -0600, Simon Glass wrote:
> Hi Tom,
>
> On 5 September 2014 11:53, Tom Rini wrote:
> > On Fri, Sep 05, 2014 at 07:30:35PM +0200, Marek Vasut wrote:
> >
> > [snip]
> >> > It's easier to work with than fitImage.
> >>
> >> In which way?
> >
> > In most developer wo
Hi Masahiro,
On 4 September 2014 23:50, Masahiro Yamada wrote:
> init_page_table
Why do you need a full page table in this code? Can you not use the
existing page table features in U-Boot?
Regards,
Simon
___
U-Boot mailing list
U-Boot@lists.denx.de
ht
Hi
On 3 September 2014 23:32, Benoît Thébaudeau
wrote:
> Some boards, like mx31pdk and tx25, require the beginning of the SPL
> code to be position-independent. For these two boards, this is because
> they use the i.MX external NAND boot, which starts by executing the
> first NAND Flash page from
From: Fabio Estevam
Commit fa9c021632473 ("mx6: add example DTB for mx6qsabreauto") introduced
'imx6q-sabreauto.dts' but it adds no real value as the dts file only contains
the 'model' and 'compatible' strings.
After this commit the final binary is also changed from 'u-boot.imx' to
'u-boot-dtb.
Hi Tom,
On 5 September 2014 11:53, Tom Rini wrote:
> On Fri, Sep 05, 2014 at 07:30:35PM +0200, Marek Vasut wrote:
>
> [snip]
>> > It's easier to work with than fitImage.
>>
>> In which way?
>
> In most developer work flows at least zImage then uImage then fitImage
> are the easiest to work with,
On Fri, Sep 05, 2014 at 07:30:35PM +0200, Marek Vasut wrote:
[snip]
> > It's easier to work with than fitImage.
>
> In which way?
In most developer work flows at least zImage then uImage then fitImage
are the easiest to work with, in that order, for ARM. For ARM64 Image
in the next release will
On 09/05/2014 01:23 AM, Wolfgang Denk wrote:
> Dear Alison Wang,
>
> In message <1409895853-17736-2-git-send-email-alison.w...@freescale.com> you
> wrote:
>>
>> +unsigned long sysclk = CONFIG_SYS_CLK_FREQ;
>> +
>> +sys_info->freq_systembus = sysclk;
>> +#ifdef CONFIG_DDR_CLK_FREQ
>> +
On Friday, September 05, 2014 at 05:50:47 PM, Scott Wood wrote:
> On Thu, 2014-09-04 at 17:01 +0200, Marek Vasut wrote:
> > On Wednesday, September 03, 2014 at 06:39:23 PM, Detlev Zundel wrote:
> > > Hi Marek,
> > >
> > > [...]
> > >
> > > > I got my talk, "Secure and flexible boot with U-Boot bo
On Thu, 2014-09-04 at 17:01 +0200, Marek Vasut wrote:
> On Wednesday, September 03, 2014 at 06:39:23 PM, Detlev Zundel wrote:
> > Hi Marek,
> >
> > [...]
> >
> > > I got my talk, "Secure and flexible boot with U-Boot bootloader",
> > > accepted for the main track it seems. It's mostly about "use
Hi Wolfgang,
On 4 September 2014 23:21, Wolfgang Denk wrote:
> Dear Simon & Ulf,
>
> In message
> you
> wrote:
>>
>> > 2) Is there a possibility to check the signature/CRC before copying the
>> > image to ram with imxtract?
>>
>> I'm not sure of the specifics here - sometimes the image must be
Hi Masahiro,
On 5 September 2014 06:03, Masahiro Yamada wrote:
> Hi Marek,
>
>
>
> On Fri, 5 Sep 2014 12:35:18 +0200
> Marek Vasut wrote:
>
>> On Friday, September 05, 2014 at 07:50:19 AM, Masahiro Yamada wrote:
>> > The driver for on-chip UART used on Panasonic UniPhier platform.
>> >
>> > Sign
The keystone_nav driver is general driver intended to be used for
working with queue manager and pktdma for different IPs like NETCP,
AIF, FFTC, etc. So the it's API shouldn't be named like it works only
with one of them, it should be general names. The names with prefix
like netcp_* rather do for
The keystone_nav is used by drivers/net/keystone_net.c driver to
send and receive packets, but currently it's placed at keystone
arch sources. So it should be in the drivers directory also.
It's separate driver that can be used for sending and receiving
pktdma packets by others drivers also.
This
Use definitions in netcp_pktdma instead direct addresses.
The definitions can be set specifically for SoC, so there
is no reason to check SoC type while initialization.
Acked-by: Vitaly Andrianov
Signed-off-by: Ivan Khoronzhuk
---
arch/arm/cpu/armv7/keystone/keystone_nav.c | 39
Use definitions in qm_config. The definitions can be set specifically
for SoC, so there is no reason to check SoC type while initialization.
Acked-by: Vitaly Andrianov
Signed-off-by: Ivan Khoronzhuk
---
arch/arm/cpu/armv7/keystone/keystone_nav.c| 49 +++
arch/arm/inc
This series generalize keystone_nav driver usage in order to
add keystone2 K2E/K2L SoCs support.
Based on u-boot-ti/master
v2..v1:
rebased on top of u-boot-ti/master, no functional changes
Ivan Khoronzhuk (4):
keystone2: keystone_nav: don't use hard addresses in qm_config
keystone2:
This patch uses generic 'load' command instead of 'fatload' for
'loadbootscript' and 'loadbootenv' as already done for 'loadimage' and
'loaduimage' for OMAP4 boards.
This allows to use EXT partition instead of FAT, while keeping FAT
compatibility.
Signed-off-by: Guillaume GARDET
(resend since I managed to forget the list in the CC, sorry about that)
The following changes since commit d6c1ffc7d23f4fe4ae8c91101861055b8e1501b6:
Prepare v2014.10-rc2 (2014-09-02 16:58:29 -0400)
are available in the git repository at:
git://git.denx.de/u-boot-sunxi.git
for you to fetch
On Friday, September 05, 2014 at 02:03:38 PM, Masahiro Yamada wrote:
> Hi Marek,
>
>
>
> On Fri, 5 Sep 2014 12:35:18 +0200
>
> Marek Vasut wrote:
> > On Friday, September 05, 2014 at 07:50:19 AM, Masahiro Yamada wrote:
> > > The driver for on-chip UART used on Panasonic UniPhier platform.
> >
On 9/5/2014 2:43 AM, Otavio Salvador wrote:
> Hello Ye,
>
> On Thu, Sep 4, 2014 at 11:17 AM, Ye.Li wrote:
>> This patch adds the i.MX6DL arm2 board support. The i.MX6DL ARM2
>> shared the same board with i.MX6Q ARM2 board since the i.MX6DL is
>> pin-pin compatible with i.MX6Q.
>>
>> The patch als
Dear Albert,
The following changes since commit d6c1ffc7d23f4fe4ae8c91101861055b8e1501b6:
Prepare v2014.10-rc2 (2014-09-02 16:58:29 -0400)
are available in the git repository at:
http://git.denx.de/u-boot-samsung
for you to fetch changes up to 5cecf21fb1fadeb39be862793f743841ad373601:
On Fri 2014-09-05 14:05:48, Marek Vasut wrote:
> On Friday, September 05, 2014 at 01:59:19 PM, Pavel Machek wrote:
> > On Fri 2014-09-05 13:40:58, Marek Vasut wrote:
> > > On Friday, September 05, 2014 at 12:49:48 PM, Pavel Machek wrote:
> > > > dw_mmc driver was responding to errors with debug().
On Friday, September 05, 2014 at 01:59:19 PM, Pavel Machek wrote:
> On Fri 2014-09-05 13:40:58, Marek Vasut wrote:
> > On Friday, September 05, 2014 at 12:49:48 PM, Pavel Machek wrote:
> > > dw_mmc driver was responding to errors with debug(). Change that to
> > > prinf so that any errors are immed
Hi Marek,
On Fri, 5 Sep 2014 12:35:18 +0200
Marek Vasut wrote:
> On Friday, September 05, 2014 at 07:50:19 AM, Masahiro Yamada wrote:
> > The driver for on-chip UART used on Panasonic UniPhier platform.
> >
> > Signed-off-by: Masahiro Yamada
>
> [...]
>
> Hi!
>
> > +static void uniphier_s
On Fri 2014-09-05 13:40:58, Marek Vasut wrote:
> On Friday, September 05, 2014 at 12:49:48 PM, Pavel Machek wrote:
> > dw_mmc driver was responding to errors with debug(). Change that to
> > prinf so that any errors are immediately obvious. Also adjust english
> > in comments.
> >
> > Signed-off-b
Hi Minkyu,
On Fri, Sep 5, 2014 at 3:33 PM, Minkyu Kang wrote:
> On 04/08/14 20:39, Ajay kumar wrote:
>> +Minkyu
>>
>> On Mon, Aug 4, 2014 at 4:49 PM, Simon Glass wrote:
>>> Hi,
>>>
>>> On 30 July 2014 03:11, Ajay Kumar wrote:
Patchset V1:
https://www.mail-archive.com/u-boot@lists.denx
On 05/09/14 20:23, Ajay Kumar wrote:
> Patchset V1:
> https://www.mail-archive.com/u-boot@lists.denx.de/msg140596.html
>
> Patchset V2:
> https://www.mail-archive.com/u-boot@lists.denx.de/msg141203.html
>
> Patchset V3:
> http://lists.denx.de/pipermail/u-boot/2014-July/183096.html
>
> Patchset V
On Friday, September 05, 2014 at 12:49:48 PM, Pavel Machek wrote:
> dw_mmc driver was responding to errors with debug(). Change that to
> prinf so that any errors are immediately obvious. Also adjust english
> in comments.
>
> Signed-off-by: Pavel Machek
>
> diff --git a/drivers/mmc/dw_mmc.c b/d
On Friday, September 05, 2014 at 07:50:19 AM, Masahiro Yamada wrote:
> The driver for on-chip UART used on Panasonic UniPhier platform.
>
> Signed-off-by: Masahiro Yamada
[...]
Hi!
> +static void uniphier_serial_putc(struct uniphier_serial *port, const char
> c) +{
> + if (c == '\n')
> +
On Friday, September 05, 2014 at 10:11:23 AM, Heiko Schocher wrote:
[...]
> > In the DFU 1.1 spec the point 4.2.1 describes the DFU MODE DEVICE
> > DESCRIPTOR.
> >
> > According to information from point 4.- "Enumeration Phase":
> >
> > "It is very important to note that the device exposes two
This patch adds DT properties for fimd and the parade bridge chip
present on peach_pit. The panel supports 1366x768 resolution.
Signed-off-by: Ajay Kumar
Acked-by: Simon Glass
Tested-by: Simon Glass
---
arch/arm/dts/exynos5420-peach-pit.dts | 30 ++
1 file changed
Enable drivers for FIMD, DP and parade bridge chip.
Signed-off-by: Ajay Kumar
---
include/configs/peach-pit.h | 10 ++
1 file changed, 10 insertions(+)
diff --git a/include/configs/peach-pit.h b/include/configs/peach-pit.h
index 76b8d7a..88c093f 100644
--- a/include/configs/peach-pit.
This patch adds missing declaration for gpio_direction_input
function, thereby helps in resolving compilation warnings.
Signed-off-by: Ajay Kumar
---
arch/arm/include/asm/arch-exynos/gpio.h |1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/include/asm/arch-exynos/gpio.h
b/arch/arm
Add initialization code for peach_pit panel, parade bridge chip,
and backlight.
Signed-off-by: Ajay Kumar
Acked-by: Simon Glass
Tested-by: Simon Glass
---
arch/arm/include/asm/arch-exynos/system.h |3 +
board/samsung/smdk5420/smdk5420.c | 129 +++--
2 files
Add get_lcd_clk and set_lcd_clk callbacks for Exynos5420 needed by
exynos video driver.
Also, configure ACLK_400_DISP1 as the parent for MUX_ACLK_400_DISP1_SUB_SEL.
Signed-off-by: Ajay Kumar
Acked-by: Simon Glass
Tested-by: Simon Glass
---
arch/arm/cpu/armv7/exynos/clock.c | 83 +
From: Vadim Bendebury
The initialization table comes from the "Illustration of I2C command
for initialing PS8625" document supplied by Parade.
Signed-off-by: Vadim Bendebury
Signed-off-by: Ajay Kumar
Acked-by: Simon Glass
Tested-by: Simon Glass
---
drivers/video/Makefile |1 +
drivers/v
On Exynos5420 and newer versions, the FIMD sysmmus are in
"on state" by default.
We have to disable them in order to make FIMD DMA work.
This patch adds the required framework to exynos_fimd driver,
and disables FIMD sysmmu on Exynos5420.
Signed-off-by: Ajay Kumar
---
arch/arm/dts/exynos54xx.dts
Patchset V1:
https://www.mail-archive.com/u-boot@lists.denx.de/msg140596.html
Patchset V2:
https://www.mail-archive.com/u-boot@lists.denx.de/msg141203.html
Patchset V3:
http://lists.denx.de/pipermail/u-boot/2014-July/183096.html
Patchset V4:
http://comments.gmane.org/gmane.comp.boot-loaders.u-bo
RPLL is needed to drive the LCD panel on Exynos5420 based boards.
Signed-off-by: Ajay Kumar
Acked-by: Simon Glass
Tested-by: Simon Glass
---
arch/arm/cpu/armv7/exynos/clock_init.h |3 +++
arch/arm/cpu/armv7/exynos/clock_init_exynos5.c | 13 +
2 files changed, 16 inser
Previously, we used to statically assign values for vl_col, vl_row and
vl_bpix using #defines like LCD_XRES, LCD_YRES and LCD_COLOR16.
Introducing the function exynos_lcd_early_init() would take care of this
assignment on the fly by parsing FIMD DT properties, thereby allowing us
to remove LCD_XRE
DDR-ODT require cfg_dram_type switch set properly as per DDR type.
T1040RDB, T1042RDB boards have DDR3L type DDR, so cfg_dram_type
should be set to OFF for DDR3L
Update t104xrdb/README for switch setting
Signed-off-by: Priyanka Jain
---
board/freescale/t104xrdb/README |6 +++---
board/freesc
When a DNS query is sent out, the ethernet packet can get directed to
the MAC address of a server that was communicated to before. This is
wrong when the previously stored MAC address corresponds to a different
server's IP address, i.e. when the IP address of the previous and the
current communica
Hello Minkyu,
On 09/05/2014 08:55 AM, Minkyu Kang wrote:
On 24/07/14 19:42, Przemyslaw Marczak wrote:
This patch changes MPLL from 800MHz to 880MHz on Odroid.
Signed-off-by: Przemyslaw Marczak
---
board/samsung/odroid/odroid.c | 60 +--
1 file change
dw_mmc driver was responding to errors with debug(). Change that to
prinf so that any errors are immediately obvious. Also adjust english
in comments.
Signed-off-by: Pavel Machek
diff --git a/drivers/mmc/dw_mmc.c b/drivers/mmc/dw_mmc.c
index 0df30bc..4c16e7f 100644
--- a/drivers/mmc/dw_mmc.c
++
Allocate request up to THOR_PACKET_SIZE not the ep0->maxpacket
as the descriptors data depend on the number of descriptors
and this 64 bytes were not enough and the buffer might overflow
which results in memalign failures later.
Signed-off-by: Siva Durga Prasad Paladugu
---
drivers/usb/gadget/f_
On 04/08/14 20:39, Ajay kumar wrote:
> +Minkyu
>
> On Mon, Aug 4, 2014 at 4:49 PM, Simon Glass wrote:
>> Hi,
>>
>> On 30 July 2014 03:11, Ajay Kumar wrote:
>>> Patchset V1:
>>> https://www.mail-archive.com/u-boot@lists.denx.de/msg140596.html
>>>
>>> Patchset V2:
>>> https://www.mail-archive.com/
Dear Alison Wang,
In message <1409895853-17736-2-git-send-email-alison.w...@freescale.com> you
wrote:
>
> + unsigned long sysclk = CONFIG_SYS_CLK_FREQ;
> +
> + sys_info->freq_systembus = sysclk;
> +#ifdef CONFIG_DDR_CLK_FREQ
> + sys_info->freq_ddrbus = CONFIG_DDR_CLK_FREQ;
> +#else
>
This patch adds board support for the Toradex Apalis T30 a computer on
module which can be used on different carrier boards.
For the sake of ease of use we do not distinguish between different
carrier boards for now as the base module features are deemed
sufficient enough for regular booting.
The
Hello Lukasz,
Am 05.09.2014 09:53, schrieb Lukasz Majewski:
Hi Heiko,
Hello Marek,
Am 05.09.2014 00:42, schrieb Marek Vasut:
On Thursday, September 04, 2014 at 12:21:40 PM, Heiko Schocher
wrote:
Hi Heiko,
I'll just rant a bit, but please wait until Lukasz does a proper
runthrough.
set bD
Hello Stefan,
Am 05.09.2014 09:57, schrieb Stefan Roese:
The ioread16_rep() and iowrite16_rep() implementations are U-Boot specific
and have been introduced with the Linux MTD v3.14 sync. While introducing
these functions, the length for the loop has been miscalculated. The ">> 1"
is already pr
The ioread16_rep() and iowrite16_rep() implementations are U-Boot specific
and have been introduced with the Linux MTD v3.14 sync. While introducing
these functions, the length for the loop has been miscalculated. The ">> 1"
is already present in the caller. So lets remove it in the function.
Test
Hi Heiko,
> Hello Marek,
>
> Am 05.09.2014 00:42, schrieb Marek Vasut:
> > On Thursday, September 04, 2014 at 12:21:40 PM, Heiko Schocher
> > wrote:
> >
> > Hi Heiko,
> >
> > I'll just rant a bit, but please wait until Lukasz does a proper
> > runthrough.
> >
> >> set bDeviceClass, bDeviceSubClas
On Fri, 2014-09-05 at 00:56 +0900, Masahiro YAMADA wrote:
> I am sorry about this, but could you rebase your patch please?
Sure, will re-base to u-boot/master and re-submit ASAP.
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/
UniPhier is the SoC family developed by Panasonic Corporation,
based on ARM Cortex-A9.
This patch set adds its SoC/board support code with some drivers.
I confirmed this series can be applied onto v2014.10-rc2 tag
and built cleanly.
Changes between v3 and v4
-
Disable
Update the ci_udc driver to support bulk transfer
and also added capability of having multiple dtds
if requested data is more thank 16K.
These changes are tested for both the DFU and lthor.
Signed-off-by: Siva Durga Prasad Paladugu
---
drivers/usb/gadget/ci_udc.c | 135 +
Dont perform reset at the end of thor download
if configured to do reset off.
Reset may not be required in all cases and hence
provided an option to do so.
Signed-off-by: Siva Durga Prasad Paladugu
---
drivers/usb/gadget/f_thor.c |7 +++
drivers/usb/gadget/f_thor.h |3 +++
2 files ch
92 matches
Mail list logo
