To save most the banter, and rephrasing:
What is the 'EXPECTED' current behavior of the 83xx/6xx architecture for the
most current 1.3.3+ GIT release of passing MACs into Linux 2.6.24. Lastly, I
am using the UEC 83xx driver.
I have defined QE_OF.
I have defined CONFIG_UEC_ETH.
I have defined CON
quick status check.
What is the current operation / priority of how MACs are passed into Linux
2.6.24+ vs the U-boot 1.3.3+ environment string?
Russell McGuire
Senior Systems Engineer
[EMAIL PROTECTED]
503.888.0968
r solutions.
-Russ
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 03, 2008 5:34 PM
To: [EMAIL PROTECTED]
Cc: 'David Hawkins'; 'Steve Hensley'; u-boot-users@lists.sourceforge.net
Subject: RE: [U-Boot-Users] 83xx SPD_EEPROM DDR2 Issues
PM
To: [EMAIL PROTECTED]
Cc: 'David Hawkins'; 'Steve Hensley'; u-boot-users@lists.sourceforge.net
Subject: RE: [U-Boot-Users] 83xx SPD_EEPROM DDR2 Issues
"Russell McGuire" <[EMAIL PROTECTED]> wrote on 06/03/2008
04:15:55 PM:
>
> I haven't gone throu
Bruce,
I think you've hit upon something here.
After checking the SPD tables during the intial comparison for data rates,
it is clear that 1) the DDR2 bit fields are not defined properly. i.e. it
looks like the big if-if-else statement specifically does not have valid
DDR2 values defined for clk_c
halt within our company due to this.
Russell McGuire
Senior Systems Engineer
[EMAIL PROTECTED]
503.888.0968
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http
All,
I wanted to post this for comments before I submitted a patch.
Anyone using the 83xx and maybe other families, may or may not have noticed
that any half duplex connection will not work, except in MII or RMII modes.
Although, I am guessing that many people never use this mode, real pain
All - Freescale crowd,
Carefully reading the manual it becomes evident, though not obvious that
current U-boot UEC driver would crash with any 10BaseT hub connected.
I.e. any RGMII connection with Half Duplex, which the current UEC driver
readily will set, is an illegal mode in the MPC83xx chipse
Freescale Crowd,
Has anyone already started implementation of the microcode patches for the
QE_ENET20 errata for U-boot?
Guessing it is not hot on the list, since it probably only affects 10BaseT
users.
If not, does anyone have any quick suggestions on where the patch should get
loaded, i.e. at
All,
Possible fix, since I am a newbie at messing with somebody elses code can
the owner of the MD5 code verify this problem / fix??
I found that if I did the following with changing some include files, this
will now compile on my older FC5 system. .
MD5 Compile Fix:
1) In file 'include/u-boot
All,
Okay, I have tracked this farther into the compilation problem.
I have no reason to believe that 'my system' is any different that any
standard stock FC5 box, other than its been original since FC5 was released,
pending updates.
Looking through the code, though I haven't nailed it, it would
All,
I have tracked my compilation issues back to several patches.
Wondering if anyone has found a work around for this, obviously a lot of us
are not seeing this issue.
Patch dated 2/29/2008, Add libfdt support to mkimage.
Then following any patches related to sha1 and md5 cause more errors rela
Not sure where exactly yet, but I have tracked this down to someplace
between Release v1.3.2 and Tag v1.3.3-rc1 is where it breaks on my FC5
machine.
Using 'git checkout -f v.1.3.xx', full clean, reconfigure, etc..
I am checking out intermediate versions now to see exactly what commit is
causing
So I have downloaded a 'fresh and clean' copy of the latest git and
configured for several existing Freescale based MPC boards.
Example:
make ARCH=ppc CROSS_COMPILE='ppc_6xx-' MPC8360ERDK_config
make ARCH=ppc CROSS_COMPILE='ppc_6xx-' all
I still get the same errors, i.e. __kernel_dev_t_ being de
All,
Just pulled the latest GIT down today <1.3.3+>, merged with my current code.
.
Anyway, all is well until the newish MD5 code attempts to compile then I get
two different types of errors.
Is this an artificat of an uncomplete merge perhaps?
Dependencies on a certain level of kernel that n
All,
This is not specific to U-boot, but can definitely be addressed within
U-boot drivers network drivers, in the Freescale 83xx crowd. If anyone has
suggestions as to a better list to post this in, let me know.
I have a working driver for 100BaseT with a National DP83763 GigE Phyter V
chipset,
All,
Just curious if anyone has done any work with this near past.
I have had an 8360E board up for several months now and been happily working
away with different types of Kingston S0-DIMM DDR2 memory.
512MB, 1204MB, DDR2 533Mhz memory. All work well, with U-boot.
Using the SPD detectetion, thin
17 matches
Mail list logo