On 8/21/07, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> From: Stephen Neuendorffer <[EMAIL PROTECTED]>
>
> In the future, this will be used to provide similar configuration
> for PowerPC and Microblaze.
I'm not convinced that this change is worth it since there is only one
in-tree driver that u
On 8/21/07, Robert Woodworth <[EMAIL PROTECTED]> wrote:
> Should the xparameters.h file *really* be included in the tree?
>
> This file is completely board/EDK/ISE/synthesis specific. I'd rather it
> not be included and have people copy theirs from EDK.
> Or as I have done, sym-link it from my
Hi, all
I am running linux-xilinx-26.git, a MontaVista embedded OS based on kernel
2.6.22, on ML403. I have made the kernel image and downloaded it into the
board. But when it ran, the system stopped after printed the message "Now
booting the kernel", and no other information was output. I ha
Should the xparameters.h file *really* be included in the tree?
This file is completely board/EDK/ISE/synthesis specific. I'd rather it
not be included and have people copy theirs from EDK.
Or as I have done, sym-link it from my EDK project.
Woody.
On Tue, 2007-08-21 at 17:53 -0700, [
On Tue, Aug 21, 2007 at 03:24:52PM +0100, Matt Sealey wrote:
> David Gibson wrote:
> > On Tue, Aug 21, 2007 at 01:58:31PM +0100, Matt Sealey wrote:
> >> David Gibson wrote:
> >>> Uh... no... this is in the bootwrapper, long before ppc_md even
> >>> exists. platform_init() is called from arch/power
On Tue, 21 Aug 2007 17:53:13 -0700
[EMAIL PROTECTED] wrote:
> From: Stephen Neuendorffer <[EMAIL PROTECTED]>
>
> xupv2p support generates MAC addresses based on a silicon serial ID.
General reminder, no new code will be accepted in arch/ppc. It's in
bugfix state only.
I of course have no probl
From: Stephen Neuendorffer <[EMAIL PROTECTED]>
xupv2p support generates MAC addresses based on a silicon serial ID.
Signed-off-by: Stephen Neuendorffer <[EMAIL PROTECTED]>
Signed-off-by: Wolfgang Reissnegger <[EMAIL PROTECTED]>
---
arch/ppc/platforms/4xx/Kconfig | 16 +
arc
From: Stephen Neuendorffer <[EMAIL PROTECTED]>
In the future, this will be used to provide similar configuration
for PowerPC and Microblaze.
Signed-off-by: Stephen Neuendorffer <[EMAIL PROTECTED]>
Signed-off-by: Wolfgang Reissnegger <[EMAIL PROTECTED]>
---
arch/ppc/platforms/4xx/Kconfig |1 +
From: Stephen Neuendorffer <[EMAIL PROTECTED]>
Make support for Xilinx boards more generic, making it easier
to add new boards. ML300 and ML403 now use this. Added
CONFIG_XILINX_EMBED_CONFIG to do the consolidation, while still
allowing boards not in the tree to avoid embed_config.
Signed-off-b
Hi, Robert, Josh
>>> Question 1:
>>> Do I need a special glibc for the Xilinx PPC 405
>>> Does a normal PPC glibc have more "advanced" instructions compiled in
>>> that will not work on a Xilinx PPC 405??
Have a look at the eglibc project (embedded glibc) at http://www.eglibc.org
I think th
Hi all.
I got the driver registered and have spent some time tracking down a IRQ
problem.
It just ignores me when it gets to 'request_irq' with a 'nobody cared'
response.
The memory appears right and the test IRQ of 3 is supposed to be correct.
I never see the HCD driver load up, does that h
David Gibson wrote:
> On Tue, Aug 21, 2007 at 01:58:31PM +0100, Matt Sealey wrote:
>> David Gibson wrote:
>>> Uh... no... this is in the bootwrapper, long before ppc_md even
>>> exists. platform_init() is called from arch/powerpc/boot/crt0.S,
>>> immediately before main().
>> Oh *THAT* platform in
On Tue, Aug 21, 2007 at 01:58:31PM +0100, Matt Sealey wrote:
>
> David Gibson wrote:
> > Uh... no... this is in the bootwrapper, long before ppc_md even
> > exists. platform_init() is called from arch/powerpc/boot/crt0.S,
> > immediately before main().
>
> Oh *THAT* platform init.
>
> So I coul
On Tue, 21 Aug 2007 11:52:35 +0300
"Stelios Koroneos" <[EMAIL PROTECTED]> wrote:
> > Question 1:
> > Do I need a special glibc for the Xilinx PPC 405
>
> FYI we are at the last stage of implementing OpenEmbedded support for the
> Xilinx ml403 (and hopefully other Xilinx boards in the near fut
David Gibson wrote:
> Uh... no... this is in the bootwrapper, long before ppc_md even
> exists. platform_init() is called from arch/powerpc/boot/crt0.S,
> immediately before main().
Oh *THAT* platform init.
So I could just drop a
} else {
dt_find_initrd();
}
.. at the end and nobody w
On 8/21/07, Computer - Service <[EMAIL PROTECTED]> wrote:
> Hi all.
>
> I try to port Linux 2.6 on my XUPV2P Board which is based on ML300.
>
> It runs sometimes, but for the usual case it just doesn't.
> My problem is the initialization.
> I have no clue why I get different values almost every tim
On Tue, Aug 21, 2007 at 01:36:49PM +0100, Matt Sealey wrote:
> David Gibson wrote:
> > On Tue, Aug 21, 2007 at 12:21:18PM +0100, Matt Sealey wrote:
> >> Damn, I should use patchwork more efficiently;
> >>
> >> http://patchwork.ozlabs.org/linuxppc/patch?q=initrd&filter=none&id=12168
> >>
> >> Does a
David Gibson wrote:
> On Tue, Aug 21, 2007 at 12:21:18PM +0100, Matt Sealey wrote:
>> Damn, I should use patchwork more efficiently;
>>
>> http://patchwork.ozlabs.org/linuxppc/patch?q=initrd&filter=none&id=12168
>>
>> Does anyone have any suggestion on the best way to integrate this so that
>> it "
Hi all.
I try to port Linux 2.6 on my XUPV2P Board which is based on ML300.
It runs sometimes, but for the usual case it just doesn't.
My problem is the initialization.
I have no clue why I get different values almost every time.
This is a log from the same zImage.elf, which is just loaded certai
Hai,
I am using the kernel 2.6.21. In the file
(arch/ppc/syslib/pci_auto.c) we have the function pciauto_bus_scan(). In
this function it will skip the host birdge. But in the arch/powepc
directory we don't have that types of file and the function
pciauto_bus_scan() also removed.
I want to k
On Tue, Aug 21, 2007 at 12:21:18PM +0100, Matt Sealey wrote:
> Damn, I should use patchwork more efficiently;
>
> http://patchwork.ozlabs.org/linuxppc/patch?q=initrd&filter=none&id=12168
>
> Does anyone have any suggestion on the best way to integrate this so that
> it "just works" on OF platform
Damn, I should use patchwork more efficiently;
http://patchwork.ozlabs.org/linuxppc/patch?q=initrd&filter=none&id=12168
Does anyone have any suggestion on the best way to integrate this so that
it "just works" on OF platforms? It seems only to be usable way too late
in boot to work, this code wou
Hi guys,
Just a query here, there was a patch for /chosen/initrd,start and initrd,end
variables gained from firmware or so, which allowed booting without getting
those values into r3/r4, does anyone know the maintainer/author of that
patch?
Also, what are the chances of pushing it for 2.6.23 or 2
Hi again,
I also work with devices on the VME bus. The approach we took is to map
> all the devices into userspace, and use Xenomai for RT performance. This
> avoids the need to write drivers for all the devices. The RT-performance
> of Xenomai is quite good: the jitter on a timer-interrupt is alw
> Question 1:
> Do I need a special glibc for the Xilinx PPC 405
FYI we are at the last stage of implementing OpenEmbedded support for the
Xilinx ml403 (and hopefully other Xilinx boards in the near future)
It also handles the EDK header copying procedure "automagically" i.e you
point to your
Konstantin Boyanov wrote:
>
> Hi again,
>
> After some googling I came to the conclusion that the best approach to
> understanding how to write a driver for a device behind a PCI-XXX
> bridge is to look at the source for the USB subsystem, although the
> USB subsystem is actually a bus subssyt
Hi again,
After some googling I came to the conclusion that the best approach to
understanding how to write a driver for a device behind a PCI-XXX bridge is
to look at the source for the USB subsystem, although the USB subsystem is
actually a bus subssytem and not a class.
Correct me if I'm wrong
27 matches
Mail list logo
