[U-Boot] LL Temac, MAC adresse trouble

[John Linn]

Sorry I'm not much help with arch/ppc kernels and u-boot.

In our case we were pulling the mac address from the i2c eeprom so I
don't think it mattered what u-boot would have been passing.

I've only been working with arch/powerpc and u-boot for some time now.
I'll let you know if I see something helpful.

-- John

> -----Original Message-----
> From: Georg Schardt [mailto:schardt at team-ctech.de]
> Sent: Wednesday, August 13, 2008 12:22 PM
> To: John Linn
> Cc: u-boot at lists.denx.de
> Subject: Re: [U-Boot] LL Temac, MAC adresse trouble
> 
> 
> I use ARCH=ppc without devicetree.
> 
> i tried the devicetree tool from git.xilinx.com but i don't understand
> it right. i miss the .py file in the git-tree ? but this is my next
> project :)
> 
> because booting without uboot works fine, i dont think there is a
> problem with the driver.
> 
> i made a new board definition for the fx12mm copy some stuff from the
> ml403 board. is there any definition i have to change ? board_info or
> something ?
> 
> Georg
> 
> John Linn wrote:
> >> -----Original Message-----
> >> From: Georg Schardt [mailto:schardt at team-ctech.de]
> >> Sent: Wednesday, August 13, 2008 12:01 PM
> >> To: John Linn; u-boot at lists.denx.de
> >> Subject: Re: [U-Boot] LL Temac, MAC adresse trouble
> >>
> >> Hi John,
> >>
> >> i use the kernel from git.xilinx.com (2.6.26-rc6) on  a Virtex4FX12
> >> Minimodul from Memec. in this kernel tree is a driver for the
lltemac
> >> included.
> >>
> >> Georg
> >>
> >>
> >
> > My mistake, I thought you were trying to use the LL TEMAC with
u-boot to
> > load the kernel.
> >
> > Are you using arch/powerpc with a device tree and passing the device
> > tree to the kernel?
> >
> > I think the mac address should be in the device tree.
> >
> > I can't say I have tested that problem before, so we might have an
issue
> > with our driver also.
> >
> > -- John
> >
> >
> >>
> >>
> >> John Linn wrote:
> >>
> >>> Hi Georg,
> >>>
> >>> Are you writing the LL TEMAC driver yourself or did you get it
> >>> somewhere?
> >>>
> >>> I am working on u-boot for Xilinx is the reason I'm asking.
> >>>
> >>> Thanks,
> >>> John
> >>>
> >>>
> >>>
> >>>> -----Original Message-----
> >>>> From: u-boot-bounces at lists.denx.de
> >>>>
> >>>>
> >>> [mailto:u-boot-bounces at lists.denx.de] On Behalf Of Georg Schardt
> >>>
> >>>
> >>>> Sent: Wednesday, August 13, 2008 11:21 AM
> >>>> To: u-boot at lists.denx.de
> >>>> Subject: [U-Boot] LL Temac, MAC adresse trouble
> >>>>
> >>>> Hi ,
> >>>>
> >>>> uh, the next error in my u-boot config :)
> >>>>
> >>>> if i boot my linux-kernel via the xmd-debugger the lltemac has a
> >>>>
> >>>>
> >>> correct
> >>>
> >>>
> >>>> mac-address and speed negotiating works fine, link comes up and
> >>>>
> > ping
> >
> >>> works.
> >>>
> >>>
> >>>> booting it with u-boot the mac-address is 0:0:0:0:0:0. i can
change
> >>>>
> >>>>
> >>> the
> >>>
> >>>
> >>>> address with ifconfig eth0 hw ether, but speed negotiation does
not
> >>>>
> >>>>
> >>> work:
> >>>
> >>>
> >>>> eth0: XLlTemac: Not able to set the speed to 1000 (status:
0x7949)
> >>>> eth0: XLlTemac: Not able to set the speed to 100 (status: 0x7949)
> >>>> eth0: XLlTemac: Not able to set the speed to 10 (status: 0x7949)
> >>>> eth0: XLlTemac: could not negotiate speed
> >>>> eth0: XLlTemac: PHY Link carrier restored.
> >>>>
> >>>> i think there is some error in the informations u-boot gives to
the
> >>>> linux kernel,  but i don't know what part of u-boot is doing
this.
> >>>>
> >>>> greetings
> >>>> georg
> >>>> _______________________________________________
> >>>> U-Boot mailing list
> >>>> U-Boot at lists.denx.de
> >>>> http://lists.denx.de/mailman/listinfo/u-boot
> >>>>
> >>>>
> >>> This email and any attachments are intended for the sole use of
the
> >>>
> > named recipient(s) and
> >
> >> contain(s) confidential information that may be proprietary,
> >>
> > privileged or copyrighted under
> >
> >> applicable law. If you are not the intended recipient, do not read,
> >>
> > copy, or forward this email
> >
> >> message or any attachments. Delete this email message and any
> >>
> > attachments immediately.
> >
> >>>
> >>>
> >
> >
> > This email and any attachments are intended for the sole use of the
named recipient(s) and
> contain(s) confidential information that may be proprietary,
privileged or copyrighted under
> applicable law. If you are not the intended recipient, do not read,
copy, or forward this email
> message or any attachments. Delete this email message and any
attachments immediately.
> >
> >
> >
> 


This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.