,
atleast i can work on that modifuying for the meanwhile.
Thanks
Rahul
Jeff Angielski
The PTR Group
-- next part --
An HTML attachment was scrubbed...
URL:
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060615/c9d743fb/attachment.htm
was scrubbed...
URL:
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060615/77df63cc/attachment.htm
Hallo!
I am not perfect in english, so please forgice me my mistakes...
I am trying to get the 2.6 kernel running on my ml403 board...
1. I downloaded paulus tree:
cg-clone git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git
myprojectdir
2. I copied my Xilinx BSP in the kernel
Hello,
I'm trying to change the order in which the MPC8248 FCC devices are bound to
network interface names.
The current behaviour is to handle FCC1, FCC2 and FCC3 in that order. FCC1 is
thus mapped to eth0 and FCC2 to eth1 (FCC3 is unused in my design).
For some reason I'd like to map FCC2
Hello again!
I had a little mistake in my first mail.
I have copied the whole BSP...
Now i have tried to copy only the xparameters_ml403.h in
arch/ppc/platforms/4xx/xparameters/ but get the same error!!
I would be more then happy when somebody could help me.
nice greetings Robert
Does it work if you plug a cable into both Ethernets? If so, then
your PHYs might not be correctly mapped.
Laurent Pinchart wrote:
Hello,
I'm trying to change the order in which the MPC8248 FCC devices are bound to
network interface names.
The current behaviour is to handle FCC1, FCC2
On Thu, 15 Jun 2006 13:59:02 +0200
Laurent Pinchart laurent.pinchart at tbox.biz wrote:
Hello,
I'm trying to change the order in which the MPC8248 FCC devices are bound to
network interface names.
The current behaviour is to handle FCC1, FCC2 and FCC3 in that order. FCC1 is
thus mapped
Hi,
I'm trying to get running linux 2.6.17-rc6 (taken from
linux-2.6-denx.git repository) on a Xilinx ml403 board.
I have a custom design in the Virtex-4 (not the reference design) with
U-Boot starting from flash without problems. I'm also able to download
the kernel image via tftp and store
/attachments/20060615/f2c94bbd/attachment.vcf
Desc: not available
Url :
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060615/9ec6f04b/attachment.vcf
:
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060615/a5ea7a29/attachment.htm
Hi,
I'm looking at the linux PCI implementation, especially MSI support
for Ocotea. And I have some observations and questions about it. Maybe
somebody here can shed some light on them. Thanks.
1. Obviously MSI is supported in Linux 2.6.x, maybe even in 2.4.x. But
MSI implementation seems to
Hi All,
I'm working with a 2.6 linux kernel in a board with a PPC405 in a Virtex
II Pro FPGA. I'm trying to generate interrupts and handle them in a
device driver that I've written.
Here is the sequence of events that happen currently:
1. I generate an interrupt by setting registers in an
Einstein
-- next part --
An HTML attachment was scrubbed...
URL:
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060615/14b9c826/attachment.htm
Benjamin Hi ! What is Ocotea ! :)
It's an eval board for some PowerPC 440 ... 440GX I think (which has
the HW capability to support MSI on PCI-X iirc)
- R.
Hi ! What is Ocotea ! :)
Did I spell it wrong?? I don't believe Ben doesn't know Ocotea.
Hmmm...Ocotea again? Let me check if I really spelled it wrong. Hey,
it's really Ocotea. ;)
Of course, there is no such MSI support specific for Ocotea.
1. Obviously MSI is supported in Linux 2.6.x,
On Thu, Jun 15, 2006 at 05:38:19PM -0400, Chris Dumoulin wrote:
Hi All,
I'm working with a 2.6 linux kernel in a board with a PPC405 in a Virtex
II Pro FPGA. I'm trying to generate interrupts and handle them in a
device driver that I've written.
Here is the sequence of events that happen
17 matches
Mail list logo
