This is a note to let you know that I've just added the patch titled
Subject: [CFT 14/29] Add vio_bus_type probe and remove methods
to my gregkh-2.6 tree. Its filename is
add-vio_bus_type-probe-and-remove-methods.patch
This tree can be found at
http://www.kernel.org/pub/linux/k
This is a note to let you know that I've just added the patch titled
Subject: [CFT 13/29] Add of_platform_bus_type probe and remove methods
to my gregkh-2.6 tree. Its filename is
add-of_platform_bus_type-probe-and-remove-methods.patch
This tree can be found at
http://www.kernel
detail:
ppc_6xx-gcc ../../../../lib/EmbedCLib/OBJ/link.x -Wall ../../../../lib/EmbedCLi
/OBJ/gcc_crt1.o -Wl,-Ttext -Wl,0x4000 -Wl,-defsym -Wl,STACK_START=0x40 -Wl
-defsym -Wl,STACK_END=0x30 -o aal25 ./OBJ_ATM/mm.o ./OBJ_ATM/mem_alloc.o .
OBJ_ATM/mem.o ./OBJ_ATM/cell.o ./OBJ_ATM/buffer.o .
Lo Chun Chung wrote:
> Dear all,
>
> I am a student from Hong Kong. Now I am doing a project about enabling a
> Bluetooth PCMCIA card (Billionton PCBTC1A-B) in a custom MPC860PC.
>
> (The custom MPC860 system is constructed by a MPC860 Processor Card and
> a custom made PCB to adding a PCMCIA
h)
-- next part --
An HTML attachment was scrubbed...
URL:
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060109/7029fb1f/attachment.htm
m really desepareted here
(PS : sorry for my bad english)
-- next part --
An HTML attachment was scrubbed...
URL:
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060109/d6b86fb5/attachment.htm
Aristeu Sergio Rozanski Filho wrote:
>Hi!
>
>
>>I'm having some trouble with the DMA allocation using Linux 2.6.14-rc2 +
>>some platform modifications. Namely, the dma_alloc_coherent() function
>>returns bogus virtual addresses causing machine check exceptions. At
>>boot, the kernel complains
Hi,
I am installing the 2.6 kernel on my 8250. I have tried a few
different versions, but none of them have any rattler-config, or
rattler-option in the platform-options of menuconfig. If anyone has any
recommendations on which kernel version to use and info on any
patches or configs for a rattler
Hi all,
I'm having some trouble with the DMA allocation using Linux 2.6.14-rc2 +
some platform modifications. Namely, the dma_alloc_coherent() function
returns bogus virtual addresses causing machine check exceptions. At
boot, the kernel complains there is something wrong, but I cannot figure
In message <200601090945.22564.david.jander at protonic.nl> you wrote:
>
> ELDK-3.1.1 has a glibc compiled with support of a certain version of the
> kernel (I guess it's 2.4.xx), so newer kernels might run (because they are
They do run.
> obviously backwards compatible), but some features of 2
Arnd Bergmann wrote:
>On Thursday 05 January 2006 21:00, mcnernbm at notes.udayton.edu wrote:
>> I finally noticed out_8 and in_8 and what not are located in the
>> ppc io.h file in the kernel development download.? But when I
>> tried to do a io.h with in my program I added #include ?
>> and it s
On Monday 09 January 2006 12:16, Fillod Stephane wrote:
> You may not include the file directly from a user-land application
> program, but you may copy/paste the in_*/out_* macros, with appropriate
> care off course.
Yes, that happens to work on some architectures, but it makes your program
not
Hello,everyboby
just looked into the 8xx fec.c sources of 2.4.18 tree and discovered
there
is a CONFIG_FEC_PACKETHOOK option. Couldnt find any further information
about it, not even the included linux/pkthook.h file. Has anyone more
information what this is for?
Hi!
> I'm having some trouble with the DMA allocation using Linux 2.6.14-rc2 +
> some platform modifications. Namely, the dma_alloc_coherent() function
> returns bogus virtual addresses causing machine check exceptions. At
> boot, the kernel complains there is something wrong, but I cannot figur
> But I can not get busybox to output a thing either run as /init or run
> as /bin/sh.
>
> I have aslo tried /bin/sash - no output.
> I have even cross compiled sash - with all kinds of "I am here"
> debugging scattered through main(), If I runn it on a powerbook, I get
> wh
David H. Lynch Jr. wrote:
> Grant Likely wrote:
>
> I have never tried to build an initrd system.
rolling up an initrd & kernel is actually very simple; but I had to read
the Makefile to figure out how to do it! I do it by copying
ramdisk.image.gz into arch/ppc/boot/images and building 'ma
On Friday 06 January 2006 16:08, Wolfgang Denk wrote:
> This is a serious misunderstanding. There is no such thing like a
> specific kernel version which is supported by the ELDK.
True, but not entirely.
ELDK-3.1.1 has a glibc compiled with support of a certain version of the
kernel (I guess
Signed-off-by: Grant C. Likely
---
arch/ppc/boot/simple/Makefile |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
a39144d5708c207f58964000baf56fa9cfb18628
diff --git a/arch/ppc/boot/simple/Makefile b/arch/ppc/boot/simple/Makefile
index f3e9c53..7abd772 100644
--- a/arch/ppc/boot/sim
Pulled from Xilinx's Linux source code. Also adds CONFIG entries to
differentiate between the VIRTEX_4_FX and VIRTEX_II_PRO where appropriate.
Signed-off-by: Grant C. Likely
---
arch/ppc/boot/simple/head.S|7 +++
arch/ppc/platforms/4xx/Kconfig | 12 +++-
2 files changed,
Signed-off-by: Grant C. Likely
---
arch/ppc/configs/ml300_defconfig | 538 ++
arch/ppc/configs/ml403_defconfig | 538 ++
2 files changed, 1076 insertions(+), 0 deletions(-)
create mode 100644 arch/ppc/configs/ml300_defco
Signed-off-by: Grant C. Likely
---
arch/ppc/boot/simple/embed_config.c | 43 +
arch/ppc/platforms/4xx/Kconfig |8 +
arch/ppc/platforms/4xx/Makefile |2
arch/ppc/platforms/4xx/xilinx_ml403.c| 177 ++
This patch only deals with the serial port definitions as there is no
support for any other xilinx IP cores in the kernel tree at the moment.
Board specific configuration moved out of virtex.[ch] and into the
xparameters.h wrapper.
Board specific XPAR values now get bound to common defines with a
Signed-off-by: Grant C. Likely
---
.../platforms/4xx/xparameters/xparameters_ml403.h | 153
+++
1 files changed, 153 insertions(+), 0 deletions(-)
create mode 100644 arch/ppc/platforms/4xx/xparameters/xparameters_ml403.h
eb36da1d3ac7f931342c95ad753220ed2aec1a8e
diff --g
Signed-off-by: Grant C. Likely
---
arch/powerpc/kernel/cputable.c | 12 +++-
1 files changed, 11 insertions(+), 1 deletions(-)
d088bba0280dacb277ec257287a83fec30b6be28
diff --git a/arch/powerpc/kernel/cputable.c b/arch/powerpc/kernel/cputable.c
index 1d85ced..3992c42 100644
--- a/arc
Signed-off-by: Grant C. Likely
---
arch/ppc/Kconfig.debug|2 -
arch/ppc/platforms/4xx/xilinx_ml300.c | 74 +++--
arch/ppc/platforms/4xx/xilinx_ml300.h |2 -
arch/ppc/syslib/Makefile |2 -
arch/ppc/syslib/xilinx_pic.c
xparameters should not be needed by anything but virtex platform code.
Move it from include/asm-ppc/ to platforms/4xx/xparameters/
This is preparing for work to remove xparameters from the dependancy tree
for most c files. xparam changes should not cause a recompile of the world.
Instead, drivers
The PPC405 hard core is used in both the Virtex-II Pro and Virtex 4 FX
FPGAs. This patch cleans up the Virtex naming convention to reflect more
than just the Virtex-II Pro.
Rename files virtex-ii_pro.[ch] to virtex.[ch]
Rename config value VIRTEX_II_PRO to XILINX_VIRTEX
Signed-off-by: Grant C. L
Here's a repost of my Xilinx ML300 and ML403 patches with a few
cleanups, a bit of patch reordering, and rebased to 2.6.15.
Changes:
- Remove xparameters.h as a dependancy to most of the kernel tree
- Rework Virtex-II Pro support to be generic for Virtex-4 also
- Move serial drivers from the OC
28 matches
Mail list logo
