Re: [U-Boot] [PATCH v3]fsl_i2c: Add i2c_board_late_init

From 16ce4f8ad545ba670898c808a765fdb8ecca5bf4 Mon Sep 17 00:00:00 2001 From: Richard Retanubun richardretanu...@ruggedcom.com Date: Mon, 12 Apr 2010 15:08:17 -0400 Subject: [PATCH] fsl_i2c: Added a callpoint for i2c_board_late_init This patch adds a callpoint in i2c_init that allows board

Re: [U-Boot] [PATCH]fsl_i2c: Add i2c_board_late_init

From d0d9e0df99ce9035db43ebcf9d48601fa6f096d4 Mon Sep 17 00:00:00 2001 From: Richard Retanubun richardretanu...@ruggedcom.com Date: Mon, 12 Apr 2010 15:08:17 -0400 Subject: [PATCH] fsl_i2c: Added a callpoint for i2c_board_late_init This patch adds a callpoint in i2c_init that allows board

Re: [U-Boot] [PATCH v2]fsl_i2c: Add i2c_board_late_init

From de1623005ece04af9082f397759fe92cbae84211 Mon Sep 17 00:00:00 2001 From: Richard Retanubun richardretanu...@ruggedcom.com Date: Mon, 12 Apr 2010 15:08:17 -0400 Subject: [PATCH] fsl_i2c: Added a callpoint for i2c_board_late_init This patch adds a callpoint in i2c_init that allows board

Re: [U-Boot] [RFC] 83xx: uec: miiphybb: Added support for bitBang SMI and uec SMI enabled at the same time.

From 1f50506ad9a305c1c9dfc68aa70551166b44d3a0 Mon Sep 17 00:00:00 2001 From: Richard Retanubun richardretanu...@ruggedcom.com Date: Wed, 17 Jun 2009 16:00:41 -0400 Subject: [PATCH] 83xx: UEC: Added support for bitBang MII driver access to PHYs This patch enabled support for having PHYs on bitBang

[U-Boot] [PATCH V3] PPC: Record uboot's relocated address in RAM and show in bdinfo.

From 58e9529fa466ef79232398aeda69373125eb2aac Mon Sep 17 00:00:00 2001 From: Richard Retanubun richardretanu...@ruggedcom.com Date: Fri, 15 Jan 2010 10:06:06 -0500 Subject: [PATCH] PPC: Record uboot's relocated address in RAM and show in bdinfo. This patch uses gd-relocaddr variable to store

[U-Boot] [PATCH] [83xx] Removed #ifdef CONFIG_MPC834X dependency on upmconfig function

Removed #ifdef CONFIG_MPC834X dependency on upmconfig function. Signed-off-by: Richard Retanubun [EMAIL PROTECTED] --- cpu/mpc83xx/cpu.c |5 - 1 files changed, 0 insertions(+), 5 deletions(-) diff --git a/cpu/mpc83xx/cpu.c b/cpu/mpc83xx/cpu.c index 99ab216..848b8fd 100644 ---

Re: [U-Boot] [PATCH v3] [83xx] Adds two more ethernet interface to 83xx

Fixed compiler warning declared but unused eth5_uec_info and eth6_uec_info. Signed-off-by: Richard Retanubun [EMAIL PROTECTED] --- Hi Ben, Thanks for applying the patch. I got a compiler warning when using it, here is a patch to fix that. Thanks for all the help Richard drivers/qe/uec.c |

Re: [U-Boot] [U-boot] [PATCHv2 1/2] NET: QE: UEC: Make uec_miiphy_read() and uec_miiphy_write() use the devname arg.

richardretanubun wrote: The current uec_miiphy_read and uec_miiphy_write hardcode access devlist[0] This patch makes these function use the devname argument that is passed in to allow access to the phy registers of other devices in devlist[]. Signed-of-by: Richard Retanubun [EMAIL PROTECTED

[U-Boot] [PATCH v3] [83xx] Adds two more ethernet interface to 83xx

Added as a convenience for other platforms that uses MPC8360 (has 8 UCC). Six eth interface is chosen because the platform I am using combines UCC12 and UCC34 as 1000 Eth and the other four UCCs as 10/100 Eth. Signed-off-by: Richard Retanubun [EMAIL PROTECTED] --- Thank you for all the feedback

Re: [U-Boot] [U-boot] [PATCHv2 1/2] NET: QE: UEC: Make uec_miiphy_read() and uec_miiphy_write() use the devname arg.

Signed-of-by: Richard Retanubun [EMAIL PROTECTED] --- drivers/qe/uec.c | 46 +++--- 1 files changed, 43 insertions(+), 3 deletions(-) diff --git a/drivers/qe/uec.c b/drivers/qe/uec.c index 344c649..e3fbbb0 100644 --- a/drivers/qe/uec.c +++

Re: [U-Boot] [U-boot] [PATCHv2 1/2] NET: QE: UEC: Make uec_miiphy_read() and uec_miiphy_write() use the devname arg.

The current uec_miiphy_read and uec_miiphy_write hardcode access devlist[0] This patch makes these function use the devname argument that is passed in to allow access to the phy registers of other devices in devlist[]. Signed-of-by: Richard Retanubun [EMAIL PROTECTED] --- Hi Ben, I'm hoping the

Re: [U-Boot] [PATCH] Add support for CONFIG_EFI_PARTITION (GUID Partition Table)

Add support for CONFIG_EFI_PARTITION (GUID Partition Table) Based on linux/fs/partitions/efi.[ch] Signed-off-by: Richard Retanubun [EMAIL PROTECTED] --- Hi Wolfgang, Boy, do I suck at submitting patches. This is the same patch as before, with some minor comment cleanup and proper formatting of

[U-Boot] [PATCH] [83xx] Adds two more ethernet interface to 83xx

Added for convenience for other platforms that uses MPC8360 (has 8 UCC). 6 eth interface is chosen because the platform I am using combines UCC12 and UCC34 as gigEth and the other 4 UCC as 10/100 Eth. - Richard From: Richard Retanubun [EMAIL PROTECTED] Date: Wed, 24 Sep 2008 17:21:47 -0400

Re: [U-Boot] [PATCH] [83xx] Adds two more ethernet interface to 83xx

Kim Phillips wrote: On Thu, 25 Sep 2008 08:53:24 -0400 richardretanubun [EMAIL PROTECTED] wrote: Added for convenience for other platforms that uses MPC8360 (has 8 UCC). 6 eth interface is chosen because the platform I am using combines UCC12 and UCC34 as gigEth and the other 4 UCC as 10

Re: [U-Boot] [PATCH v2] [83xx] Adds two more ethernet interface to 83xx

Added for convenience for other platforms that uses MPC8360 (has eight UCC). Six eth interface is chosen because the platform I am using combines UCC12 and UCC34 as two gigEth and the other four UCC as 10/100 Eth. Signed-off-by: Richard Retanubun [EMAIL PROTECTED] --- V2 of this patch adds

Re: [U-Boot] [PATCH v2] [83xx] Adds two more ethernet interface to 83xx

Wolfgang Denk wrote: Dear richardretanubun, In message [EMAIL PROTECTED] you wrote: +++ b/README @@ -1097,6 +1097,9 @@ The following options need to be configured: CONFIG_ETHADDR CONFIG_ETH2ADDR CONFIG_ETH3ADDR +CONFIG_ETH4ADDR

Re: [U-Boot] [PATCH] Add support for CONFIG_EFI_PARTITION (GUID Partition Table)

Dear Wolfgang, Andrew Dyer wrote: Also, please enlighten me: what is EFI, and what is a GUID partition table, and which systems do use that? EFI is the PC BIOS replacement that Intel came up with, most notably used on Apple's Intel based computers. A blurb about EFI is here -

Re: [U-Boot] [PATCH] Add support for CONFIG_EFI_PARTITION (GUID Partition Table)

Hi Wolfgang Andrew Dyer wrote: Also, please enlighten me: what is EFI, and what is a GUID partition table, and which systems do use that? EFI is the PC BIOS replacement that Intel came up with, most notably used on Apple's Intel based computers. A blurb about EFI is here -

Re: [U-Boot] [U-boot] [PATCHv2 1/2] NET: QE: UEC: Make uec_miiphy_read() and uec_miiphy_write() use the devname arg.

Hi Ben, Ben Warren wrote: Hi Richard, richardretanubun wrote: Hi Ben, Thanks for the feedback. I've made the changes you suggested. Here is the patch re-pasted (please let me know if this is not the proper way to submit patch v2). I started

Re: [U-Boot] [U-boot] [PATCH 2/2] NET: QE: UEC: Allow uec re-initialization based on netretry environment variable.

Hi Ben, Ben Warren wrote: Hi Richard, richardretanubun wrote: Allow uec_init to run more than once, based on the netretry environment variable. This allows for manual (back and forth) switching between network interfaces. My general issue with this patch

[U-Boot] [Query] NET: QE: UEC: Checking patch status

Dear Ben, Sorry to nag, I'm just checking in to see if you plan to push the patches I submitted, the last discussion on them are listed below: 1. [U-boot] [PATCHv2 1/2] NET: QE: UEC: Make uec_miiphy_read() and uec_miiphy_write() use the devname arg.

[U-Boot] [PATCH 1/1] CONFIG_MENUKEY: RFC: Is this how CONFIG_MENUKEY supposed to work?

I noticed that CONFIG_MENUKEY aborts autoboot unconditionally and executes the menucmd env.variable if it found a match later on. This seems odd. It is possible that I misunderstood the intent of the logic. The only other user of it now is AmigaOneG3SE. I made a patch to make the logic only

Re: [U-Boot] [U-boot] [PATCH 2/2] NET: QE: UEC: Allow uec re-initialization based on netretry environment variable.

Hi Ben, Ben Warren wrote: richardretanubun wrote: Allow uec_init to run more than once, based on the netretry environment variable. This allows for manual (back and forth) switching between network interfaces. Can't you do this by changing the 'ethactive' environment variable? You