* Re: VFS: Cannot open root device "31:03" or unknown-block(31,3)
From: HappyPhot @ 2006-01-06 14:09 UTC (permalink / raw)
To: David Jander; +Cc: linuxppc-embedded
In-Reply-To: <200601050852.45616.david.jander@protonic.nl>
> in your .config:
>
>> CONFIG_JFFS2_FS=m
>
> This is wrong. You have to choose "y", not "m" (for module).
> This way jffs2 is compiled as a module. That means, that jffs2 filesystem
> will
> not be available until the module is loaded with "insmod jffs2" of
> something
> similar. That in turn means that your system has to start up first in
> order
> to be able to do this, but since you can't start because your root
> filesystem
> is on jffs2, you have created yourself a "chicken and egg" problem.
> If you choose "y" then jffs2 support will be compiled into the kernel, and
> thus be available before booting.
Hi, David,
Yes, you are right. After changing it to 'y', the " VFS: Cannot open
root..."
message was gone. I'm so happy and thank you very much.
Now it is another problem again. (something like: Oops: kernel access of
bad
area. sig:11...). I am going to check what happened.
>
> In your bootlog:
>
>> Linux version 2.6.14.2 (happy@sddlinux1) (gcc version 3.3.3 (DENX ELDK
>> 3.1.1
>> 3.3.3-10)) #29 Sun Jan 1 22:34:28 CST 2006
>> Motorola SPS Sandpoint Test Platform
>
> I see you are using DENX ELDK 3.1.1 and a kernel which AFAIK is not
> supported
> by this version of ELDK. Are you sure this is supposed to work? It
> probably
> will, but I don't know what the "Sandpoint" is (it looks like a PowerPC
> processor of the MPC7xx series to me), so I couldn't tell.
Do you know where to get the infomation about which kernel version it
supports?
thank you,
/HappyPhot
^ permalink raw reply
* Re: How to enable PHY
From: Mark Chambers @ 2006-01-06 13:41 UTC (permalink / raw)
To: linuxppc-embedded, batsayan.das
In-Reply-To: <OF114C07C5.7CED9F64-ON652570EE.00481B82-652570EE.00489CCF@tcs.com>
[-- Attachment #1: Type: text/plain, Size: 681 bytes --]
>I found that ADS8260 board enables PHY by the following lines of code
>
>#ifndef CONFIG_ADS8260
> /* Enable the PHY.
> */
> *(volatile uint *)(BCSR_ADDR + 4) &= ~BCSR1_FETHIEN;
> *(volatile uint *)(BCSR_ADDR + 4) |= BCSR1_FETH_RST;
>#endif
>
>Our board does not have BCSR. My question is how to enable PHY for MPC8260 based customs board without BCSR?
If your board does not have the BCSR you can just leave this code out. Usually, you only need to configure which MDII
interface your PHY is connected to and which IRQ it uses. But of course I don't know how your PHY is wired up on your
custom board.
Mark Chambers
[-- Attachment #2: Type: text/html, Size: 2022 bytes --]
^ permalink raw reply
* How to enable PHY
From: batsayan.das @ 2006-01-06 13:13 UTC (permalink / raw)
To: linuxppc-embedded
[-- Attachment #1: Type: text/plain, Size: 1018 bytes --]
Hi,
I found that ADS8260 board enables PHY by the following lines of code
#ifndef CONFIG_ADS8260
/* Enable the PHY.
*/
*(volatile uint *)(BCSR_ADDR + 4) &= ~BCSR1_FETHIEN;
*(volatile uint *)(BCSR_ADDR + 4) |= BCSR1_FETH_RST;
#endif
Our board does not have BCSR. My question is how to enable PHY for MPC8260
based customs board without BCSR?
Thanks,
Batsayan Das
Tata Consultancy Services Limited
Mailto: batsayan.das@tcs.com
Website: http://www.tcs.com
Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you
[-- Attachment #2: Type: text/html, Size: 1642 bytes --]
^ permalink raw reply
* Re: io.h question
From: Arnd Bergmann @ 2006-01-06 12:03 UTC (permalink / raw)
To: linuxppc-embedded
In-Reply-To: <OF4583615F.8ED595CE-ON852570ED.00736A17-852570ED.00736A1D@notes.udayton.edu>
On Thursday 05 January 2006 21:00, mcnernbm@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 <asm/io.h>
> and it seems to find it with not problems but it can not find the
> functions with in that file. Am i missing a define I need to set
> or something so I can see the right files with in io.h I am
> compiling for a ppc405 on a xilinx virtex 4 board.
The definitions in that file are only usable from inside the kernel,
you can not use them in a user space application.
The correct way to solve your problem (which you did not explain, so
I can only guess) would be to write a kernel device driver for
the peripherial you want to drive, at least if it does not exist yet.
For prototyping, you can play with mmap() on /dev/mem in a user
application, but that is often not very reliable.
Arnd <><
^ permalink raw reply
* Help on LXT971 eth initialization
From: batsayan.das @ 2006-01-06 10:43 UTC (permalink / raw)
To: linuxppc-embedded
[-- Attachment #1: Type: text/plain, Size: 1085 bytes --]
Hi,
My MPC8260 customs board has LXT971 Ethernet chip on FCC1. I am able to
get the linux prompt, but I am unable to initialize ethernet. I have tried
different bootarg options (like setenv bootargs ip=dhcp etc) and
different kernel compilation options (like from make menuconfig, Network
Option->enable DHCP support etc), but none enables the ethernet interface.
Any help will be appreciated.
FYI, the ethernet is working from U-Boot.
Thanks,
Batsayan Das
Tata Consultancy Services Limited
Mailto: batsayan.das@tcs.com
Website: http://www.tcs.com
Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you
[-- Attachment #2: Type: text/html, Size: 1448 bytes --]
^ permalink raw reply
* Re: Help need: Porting Linux to PQ2FADS_ZU board
From: Wolfgang Denk @ 2006-01-06 10:13 UTC (permalink / raw)
To: zengshuai; +Cc: ppc
In-Reply-To: <23894955.1136537390660.JavaMail.postfix@mx3.mail.sohu.com>
In message <23894955.1136537390660.JavaMail.postfix@mx3.mail.sohu.com> you wrote:
>
> My board is PQ2FADS_ZU.Does the ELDK not support it?
ELDK is, as the name suggests, a Development Toolkit, i. e. a
toolchain. As such, it is independent from the hardware and doesn not
support any specific board, or, if you like, it supports all boards,
even those that don't exist yet.
What you are asking for is board support in a specific kernel tree.
There is no specific support for the PQ2FADS_ZU board in our
linuxppc_2_4_devel tree (which is included with the ELDK
distribution). On the other hand this is a standard board which which
is probably working fine, but we never tested or varified it.
I guess that it is not configured for use with U-Boot.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
"Never give in. Never give in. Never. Never. Never."
- Winston Churchill
^ permalink raw reply
* Re: How to compile freescale example programs using eldk?
From: Wolfgang Denk @ 2006-01-06 10:08 UTC (permalink / raw)
To: zengshuai; +Cc: ppc
In-Reply-To: <6251452.1136535834574.JavaMail.postfix@mx3.mail.sohu.com>
In message <6251452.1136535834574.JavaMail.postfix@mx3.mail.sohu.com> you wrote:
>
> Them aren't linux drvier but for bareboard. How can I compile them using eldk?
You do it exactly the same way like you do it with any other compiler
toolchain.
If the tools come with Makefiles and Linker scripts for GNU gcc and
ld then you are set. If not, you will have to come up with your own
build rules and linker commands.
You can check how U-Boot code (especially the standalone programs)
gets linked, but be warned, this is not exactly trivial. You have to
understand what you are doing, and how the linker works.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Just because your doctor has a name for your condition doesn't mean
he knows what it is.
^ permalink raw reply
* Re: [PM-SPAM] Help need: Porting Linux to PQ2FADS_ZU board
From: KokHow Teh @ 2006-01-06 9:09 UTC (permalink / raw)
To: linuxppc-embedded
>bootargs=root=/dev/nfs rw nfsroot=172.17.248.253:/opt/eldk3/ppc_6xx
ip=172.17.24
>8.244:172.17.248.253:172.17.248.253:255.255.255.0:pq2fads::off
add console=/dev/ttyS0,115200n8 and see if it works?
^ permalink raw reply
* Help need: Porting Linux to PQ2FADS_ZU board
From: zengshuai @ 2006-01-06 8:49 UTC (permalink / raw)
To: ppc
I use ELDK3.1.1(2005-06-07).
There is a u-boot 1.1.3 and a linux 2.4.25 in the eldk.
I has compile u-boot successfully.And it works good.
I has compile kernel successfully too.(make ads8260_config)
But it doesn't work.
Detail:
-------------------------------------------------------------------------
U-Boot 1.1.3 (Dec 27 2005 - 19:35:12)
MPC8260 Reset Status: Check Stop, External Soft, External Hard
MPC8260 Clock Configuration
- Bus-to-Core Mult 4.5x, VCO Div 2, 60x Bus Freq 22-65 , Core Freq 100-300
- dfbrg 1, corecnf 0x07, busdf 5, cpmdf 1, plldf 0, pllmf 5
- vco_out 600000000, scc_clk 150000000, brg_clk 37500000
- cpu_clk 450000000, cpm_clk 300000000, bus_clk 100000000
- pci_clk 50000000
CPU: MPC8260 (HiP7 Rev 13, Mask 0.1 1K49M) at 450 MHz
Board: Motorola PQ2FADS-ZU
DRAM: 32 MB
FLASH: 8 MB
In: serial
Out: serial
Err: serial
Net: FCC2 ETHERNET
Hit any key to stop autoboot: 0
=> printenv
bootdelay=5
baudrate=115200
ethact=FCC2 ETHERNET
ethaddr=0A:00:00:00:00:0A
gatewayip=172.17.248.1
netmask=255.255.255.0
ipaddr=172.17.248.244
serverip=172.17.248.253
bootcmd=tftp 100000 vmlinux.UBoot; bootm 100000
bootargs=root=/dev/nfs rw nfsroot=172.17.248.253:/opt/eldk3/ppc_6xx ip=172.17.24
8.244:172.17.248.253:172.17.248.253:255.255.255.0:pq2fads::off
stdin=serial
stdout=serial
stderr=serial
Environment size: 398/262140 bytes
=> boot
Using FCC2 ETHERNET device
TFTP from server 172.17.248.253; our IP address is 172.17.248.244
Filename 'vmlinux.UBoot'.
Load address: 0x100000
Loading: #################################################################
#########################################################
done
Bytes transferred = 623547 (983bb hex)
## Booting image at 00100000 ...
Image Name: Linux-2.4.25
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 623483 Bytes = 608.9 kB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
-----------------------------------------------------------------------------------
At here,it stoped.
Later,I debug the kernel using bdi2000.
I bi start_kernel(),and setp by setp.
But printk(".........) didn't work.
My board is PQ2FADS_ZU.Does the ELDK not support it?
------------------------------
我现在使用Sogou.com的2G邮箱了，你也来试试吧!
http://mail.sogou.com/recommend/sogoumail_invite_reg1.jsp?from=sogouinvitation&s_EMAIL=zengshuai%40sogou.com&username=linuxppc-embedded&FullName=linuxppc-embedded&Email=linuxppc-embedded%40ozlabs.org&verify=755eff4e640bdcfc57d93cbd8b0a9cb7
^ permalink raw reply
* How to compile freescale example programs using eldk?
From: zengshuai @ 2006-01-06 8:23 UTC (permalink / raw)
To: ppc
I down some freescale example programs at
http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=MPC8260&nodeId=02VS0lDFTQJk192977
Device Drivers
ID and Description Vendor ID Format Size K Rev # Availability
MPC8260API
PowerQUICC II API (Drivers and Examples)
Includes support for PCI, AAL2, AAL5, MSP, and more(10/03/2002) FREESCALE zip 15785 4.0.2
Them aren't linux drvier but for bareboard. How can I compile them using eldk?
------------------------------
我现在使用Sogou.com的2G邮箱了，你也来试试吧!
http://mail.sogou.com/recommend/sogoumail_invite_reg1.jsp?from=sogouinvitation&s_EMAIL=zengshuai%40sogou.com&username=linuxppc-embedded&FullName=linuxppc-embedded&Email=linuxppc-embedded%40ozlabs.org&verify=755eff4e640bdcfc57d93cbd8b0a9cb7
^ permalink raw reply
* Re: [PATCH] powerpc: Add PowerMac platform function interpreter
From: Benjamin Herrenschmidt @ 2006-01-05 22:19 UTC (permalink / raw)
To: Andreas Schwab; +Cc: linuxppc64-dev, linuxppc-dev list
In-Reply-To: <jeirsy4xmm.fsf@sykes.suse.de>
On Thu, 2006-01-05 at 14:23 +0100, Andreas Schwab wrote:
> Benjamin Herrenschmidt <benh@kernel.crashing.org> writes:
>
> > Anyway, here it is, comments welcome...
>
> To which tree is this relative? Neither 2.6.15 nor Linus' tree matches.
powerpc.git
Ben.
^ permalink raw reply
* io.h question
From: mcnernbm @ 2006-01-05 21:00 UTC (permalink / raw)
To: linuxppc-embedded
[-- Attachment #1: Type: text/html, Size: 606 bytes --]
^ permalink raw reply
* [PATCH 6/82] remove linux/version.h include from arch/ppc
From: J Bucknell @ 2006-01-05 20:31 UTC (permalink / raw)
To: linuxppc-dev
[-- Attachment #1: Type: text/plain, Size: 13 bytes --]
please remove
[-- Attachment #2: Type: text/html, Size: 326 bytes --]
^ permalink raw reply
* [PATCH] fix ML300 zImage in 2.6.15
From: Grant Likely @ 2006-01-05 17:48 UTC (permalink / raw)
To: trini, linuxppc-embedded
2.6.15 doesn't build a bootable zImage for the ML300 because
embed_config.o is no longer linked in. This patch adds it back in.
Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
diff --git a/arch/ppc/boot/simple/Makefile b/arch/ppc/boot/simple/Makefile
index f3e9c53..5699659 100644
--- a/arch/ppc/boot/simple/Makefile
+++ b/arch/ppc/boot/simple/Makefile
@@ -188,6 +188,7 @@ OBJCOPY_ARGS := -O elf32-powerpc
boot-y := head.o relocate.o $(extra.o-y) $(misc-y)
boot-$(CONFIG_REDWOOD_5) += embed_config.o
boot-$(CONFIG_REDWOOD_6) += embed_config.o
+boot-$(CONFIG_XILINX_ML300) += embed_config.o
boot-$(CONFIG_8xx) += embed_config.o
boot-$(CONFIG_8260) += embed_config.o
boot-$(CONFIG_BSEIP) += iic.o
--
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
(403) 663-0761
^ permalink raw reply related
* Re: How to build the zImage.prep was Re: Bug#345424 acknowledged by developer (Bug#345424: fixed in linux-2.6 2.6.15-1)
From: Grant Likely @ 2006-01-05 16:04 UTC (permalink / raw)
To: Sebastian Heutling; +Cc: linuxppc-dev
In-Reply-To: <43BCFA15.5070304@gmx.de>
Sebastian Heutling wrote:
> Hi Sven,
>
> Before trying to build a kernel myself I tried the debian linux binary
> image. An image for powerpc is not there yet so I used rc7. I netbooted
> "/boot/vmlinuz-2.6.15-rc7-powerpc" and the result was that I got a lot
> of output saying that there is something wrong. I assume the output was
> from the firmware because the kernel usually doesn't report an endless
> list of errors saying something about "stack exception" every now and
> then and mostly printing zeros followed by a new line character.
Have you tried 2.6.14? I'm having a similar issue with PReP images
using QEMU. 2.6.14 works, but 2.6.15 is busted. It *might* be the same
issue.
http://ozlabs.org/pipermail/linuxppc-dev/2005-December/020782.html
I was able to use git-bisect to narrow it down to 20 or so changes, but
I didn't get any farther.
Cheers,
g.
--
Grant Likely, B.Sc. P.Eng.
Secret Lab Technologies Ltd.
(403) 663-0761
^ permalink raw reply
* Re: [PATCH] boot/common/util.S: Put flush_{instruction, data}_cache back in .relocate_code section
From: Tom Rini @ 2006-01-05 15:05 UTC (permalink / raw)
To: Paul Janzen; +Cc: paulus, linuxppc-embedded
In-Reply-To: <oqbqyrp6zj.fsf@merlin.sez.to>
On Wed, Jan 04, 2006 at 09:40:48PM -0800, Paul Janzen wrote:
> In 2.6.14, we had the following definition of _GLOBAL() in
> include/asm-ppc/processor.h:
>
> #define _GLOBAL(n)\
> .stabs __stringify(n:F-1),N_FUN,0,0,n;\
> .globl n;\
> n:
>
> In 2.6.15, as part of the great powerpc merge, we moved this definition to
> include/asm-powerpc/ppc_asm.h, where it appears (to 32-bit code) as:
>
> #define _GLOBAL(n) \
> .text; \
> .stabs __stringify(n:F-1),N_FUN,0,0,n;\
> .globl n; \
> n:
>
> Mostly, this is fine. However, we also have the following, in
> arch/ppc/boot/common/util.S:
>
> .section ".relocate_code","xa"
> [...]
> _GLOBAL(flush_instruction_cache)
> [...]
> _GLOBAL(flush_data_cache)
> [...]
>
> The addition of the .text section definition in the definition of
> _GLOBAL overrides the .relocate_code section definition. As a result,
> these two functions don't end up in .relocate_code, so they don't get
> relocated correctly, and the boot fails.
>
> There's another suspicious-looking usage at kernel/swsusp.S:37 that
> someone should look into. I did not exhaustively search the source
> tree, though.
>
> The following is the minimal patch that fixes the immediate problem.
> I could easily be convinced that the _GLOBAL definition should be
> modified to remove the ".text;" line either instead of, or in addition
> to, this fix.
>
> Signed-off-by: Paul Janzen <pcj@linux.sez.to>
Thanks for tracking this one down. Paul, can you please make sure this
gets to Linus and the stable team? Thanks.
Acked-by: Tom Rini <trini@kernel.crashing.org>
> --- arch/ppc/boot/common/util.S~ 2005-12-24 15:47:48.000000000 -0800
> +++ arch/ppc/boot/common/util.S 2006-01-04 14:07:12.000000000 -0800
> @@ -234,7 +234,8 @@ udelay:
> * First, flush the data cache in case it was enabled and may be
> * holding instructions for copy back.
> */
> -_GLOBAL(flush_instruction_cache)
> + .globl flush_instruction_cache
> +flush_instruction_cache:
> mflr r6
> bl flush_data_cache
>
> @@ -279,7 +280,8 @@ _GLOBAL(flush_instruction_cache)
> * Flush data cache
> * Do this by just reading lots of stuff into the cache.
> */
> -_GLOBAL(flush_data_cache)
> + .globl flush_data_cache
> +flush_data_cache:
> lis r3,cache_flush_buffer@h
> ori r3,r3,cache_flush_buffer@l
> li r4,NUM_CACHE_LINES
>
> -- Paul
--
Tom Rini
http://gate.crashing.org/~trini/
^ permalink raw reply
* [CFT 19/29] Add macio_bus_type probe and remove methods
From: Russell King @ 2006-01-05 14:39 UTC (permalink / raw)
To: LKML; +Cc: Greg K-H, MAC
In-Reply-To: <20060105142951.13.01@flint.arm.linux.org.uk>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
---
drivers/macintosh/macio_asic.c | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff -up -x BitKeeper -x ChangeSet -x SCCS -x _xlk -x *.orig -x *.rej -x .git linus/drivers/macintosh/macio_asic.c linux/drivers/macintosh/macio_asic.c
--- linus/drivers/macintosh/macio_asic.c Sun Nov 6 22:16:28 2005
+++ linux/drivers/macintosh/macio_asic.c Sun Nov 13 16:28:39 2005
@@ -204,6 +204,9 @@ struct bus_type macio_bus_type = {
.name = "macio",
.match = macio_bus_match,
.hotplug = macio_hotplug,
+ .probe = macio_device_probe,
+ .remove = macio_device_remove,
+ .shutdown = macio_device_shutdown,
.suspend = macio_device_suspend,
.resume = macio_device_resume,
.dev_attrs = macio_dev_attrs,
@@ -487,9 +490,6 @@ int macio_register_driver(struct macio_d
/* initialize common driver fields */
drv->driver.name = drv->name;
drv->driver.bus = &macio_bus_type;
- drv->driver.probe = macio_device_probe;
- drv->driver.remove = macio_device_remove;
- drv->driver.shutdown = macio_device_shutdown;
/* register with core */
count = driver_register(&drv->driver);
^ permalink raw reply
* [CFT 14/29] Add vio_bus_type probe and remove methods
From: Russell King @ 2006-01-05 14:36 UTC (permalink / raw)
To: LKML; +Cc: Greg K-H, PPC
In-Reply-To: <20060105142951.13.01@flint.arm.linux.org.uk>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
---
arch/powerpc/kernel/vio.c | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
diff -up -x BitKeeper -x ChangeSet -x SCCS -x _xlk -x *.orig -x *.rej -x .git linus/arch/powerpc/kernel/vio.c linux/arch/powerpc/kernel/vio.c
--- linus/arch/powerpc/kernel/vio.c Wed Nov 9 19:20:14 2005
+++ linux/arch/powerpc/kernel/vio.c Sun Nov 13 16:14:10 2005
@@ -76,7 +76,7 @@ static void vio_bus_shutdown(struct devi
struct vio_dev *viodev = to_vio_dev(dev);
struct vio_driver *viodrv = to_vio_driver(dev->driver);
- if (viodrv->shutdown)
+ if (dev->driver && viodrv->shutdown)
viodrv->shutdown(viodev);
}
@@ -91,9 +91,6 @@ int vio_register_driver(struct vio_drive
/* fill in 'struct driver' fields */
viodrv->driver.bus = &vio_bus_type;
- viodrv->driver.probe = vio_bus_probe;
- viodrv->driver.remove = vio_bus_remove;
- viodrv->driver.shutdown = vio_bus_shutdown;
return driver_register(&viodrv->driver);
}
@@ -295,4 +292,7 @@ struct bus_type vio_bus_type = {
.name = "vio",
.hotplug = vio_hotplug,
.match = vio_bus_match,
+ .probe = vio_bus_probe,
+ .remove = vio_bus_remove,
+ .shutdown = vio_bus_shutdown,
};
^ permalink raw reply
* [CFT 13/29] Add of_platform_bus_type probe and remove methods
From: Russell King @ 2006-01-05 14:36 UTC (permalink / raw)
To: LKML; +Cc: Greg K-H, PowerPC
In-Reply-To: <20060105142951.13.01@flint.arm.linux.org.uk>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
---
arch/powerpc/kernel/of_device.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff -up -x BitKeeper -x ChangeSet -x SCCS -x _xlk -x *.orig -x *.rej -x .git linus/arch/powerpc/kernel/of_device.c linux/arch/powerpc/kernel/of_device.c
--- linus/arch/powerpc/kernel/of_device.c Mon Oct 31 07:31:59 2005
+++ linux/arch/powerpc/kernel/of_device.c Sun Nov 13 16:12:38 2005
@@ -132,6 +132,8 @@ static int of_device_resume(struct devic
struct bus_type of_platform_bus_type = {
.name = "of_platform",
.match = of_platform_bus_match,
+ .probe = of_device_probe,
+ .remove = of_device_remove,
.suspend = of_device_suspend,
.resume = of_device_resume,
};
@@ -150,8 +152,6 @@ int of_register_driver(struct of_platfor
/* initialize common driver fields */
drv->driver.name = drv->name;
drv->driver.bus = &of_platform_bus_type;
- drv->driver.probe = of_device_probe;
- drv->driver.remove = of_device_remove;
/* register with core */
count = driver_register(&drv->driver);
^ permalink raw reply
* Re: powerpc vs ppc build
From: Arnd Bergmann @ 2006-01-05 13:59 UTC (permalink / raw)
To: linuxppc-embedded; +Cc: David Jander
In-Reply-To: <200601050905.57377.david.jander@protonic.nl>
On Thursday 05 January 2006 08:05, David Jander wrote:
> Looks to me like ppc and ppc64 are deprecated and "phased out" in favour of
> powerpc.
ppc64 is no more in 2.6.15, building the kernel on a ppc64 system
will automatically use ARCH=powerpc.
> If you look at the contents of both the include/asm-ppc and
> include/asm-powerpc directories over the last revisions for example, you'll
> see files moving from asm-ppc to asm-powerpc. Now, they are in a kind of flux
> still, so you'll probably find yourself doing silly things like "ln -s
> include/asm-powerpc/* include/asm-ppc/" to keep things working and compiling
> nicely.
That should never be needed. You should always be able to do both
$ make ARCH=ppc randomconfig O=../obdir1 && make ARCH=ppc O=../obdir2
and
$ make ARCH=powerpc randomconfig O=../objdir2 && make ARCH=powerpc O=../obdir2
and build successfully with that. If it doesn't, report a bug.
> I do hope this is over soon.
I fear it might take a somewhat longer time. AFAICS, the idea is to
remove all platforms from ppc, one at a time, as soon as they are
working well enough with ARCH=powerpc or are known to be unmaintained.
At that point, the arch/ppc/ tree can be removed completely.
The catch is that this needs work from each platform maintainer that
wants his hardware to be supported in future kernels (or at least the
information that he/she doesn't care if it gets removed).
> On Wednesday 04 January 2006 23:44, Jeff Angielski wrote:
> > Is there a summary of the differences between the ppc and powerpc builds
> > for the 2.6 kernels? Or something describing what the community, in
> > general, is trying to fix/address with the different schemes - besides
> > the merging of ppc and ppc64?
I'm only a ppc64 person, so I don't know the state that the current
51 platform types from arch/ppc/Kconfig or any of the out-of-tree
ones are in, but if you are maintaining one of them that does not yet
work with ARCH=powerpc, I suggest you do the following:
1. If the platform is not already based on open firmware or the equivalent
flat device tree representation, build a device tree for it, using the
specification from http://ozlabs.org/~dgibson/dtc/ (you need to use
git to check out the repository).
2. See if there is already a platform type for your hardware present
in arch/powerpc. Note that a powerpc platform is a lot more generic
than a ppc machine type, so you almost never need to add a new one here.
E.g. every board based on a 4xx should be able to use the same platform
type.
The rule is that enabling support for some hardware should never force
you to disable support for other hardware.
3. Move over all device drivers that are still missing in powerpc.
Make sure that the drivers don't contain any hardcoded assumptions
about your hardware that may be different for other board. I/O
addresses and such stuff should come from the device tree. Moreover,
the driver should not touch any I/O if someone loads it on a board
that does not have the device.
4. Submit a patch series to linuxppc-dev that integrates your changes,
following Documentation/SubmittingPatches, and mark your arch/ppc code
as deprecated with a deadline saying at what time it will be removed
(or remove it right away with another patch).
Arnd <><
^ permalink raw reply
* Re: [PATCH] powerpc: Add PowerMac platform function interpreter
From: Andreas Schwab @ 2006-01-05 13:23 UTC (permalink / raw)
To: Benjamin Herrenschmidt; +Cc: linuxppc64-dev, linuxppc-dev list
In-Reply-To: <1136439584.4840.48.camel@localhost.localdomain>
Benjamin Herrenschmidt <benh@kernel.crashing.org> writes:
> Anyway, here it is, comments welcome...
To which tree is this relative? Neither 2.6.15 nor Linus' tree matches.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
^ permalink raw reply
* Re: How to build the zImage.prep was Re: Bug#345424 acknowledged by developer (Bug#345424: fixed in linux-2.6 2.6.15-1)
From: Sebastian Heutling @ 2006-01-05 12:59 UTC (permalink / raw)
To: Sven Luther; +Cc: linuxppc-dev
In-Reply-To: <20060105110523.GA21982@localhost.localdomain>
Sven Luther wrote:
> On Thu, Jan 05, 2006 at 11:51:01AM +0100, Sebastian Heutling wrote:
>
>>Hi Sven,
>>
>>maybe I'm just stupid - but I am not able to get an image built that can
>
>
> No, you just fail to read the manual :)
>
> please : man mkvmlinuz :)
Uhm! I didn't even think about that. I was just used to that somewhere
under arch/ppc/ is a zImage.prep after doing a "make zImage".
But anyway: Switching to shame mode. ;)
Sebastian
^ permalink raw reply
* Re: How to build the zImage.prep was Re: Bug#345424 acknowledged by developer (Bug#345424: fixed in linux-2.6 2.6.15-1)
From: Sven Luther @ 2006-01-05 11:05 UTC (permalink / raw)
To: Sebastian Heutling; +Cc: linuxppc-dev
In-Reply-To: <43BCFA15.5070304@gmx.de>
On Thu, Jan 05, 2006 at 11:51:01AM +0100, Sebastian Heutling wrote:
> Hi Sven,
>
> maybe I'm just stupid - but I am not able to get an image built that can
No, you just fail to read the manual :)
please : man mkvmlinuz :)
mkvmlinuz allows to build the zImage.prep from the vmlinux outside of the
kernel build process, which is what we are doing, otherwise the zImage.prep
may indeed be the way to handle this.
> be netbooted or put into the prep-bootloader partition. Looking at the
> sources I wonder how you do it for the debian linux-images-* as the only
> Makefile where it seems to generate a "zImage.prep" automagically is in
> arch/ppc/boot/simple/Makefile. But that doesn't work, I guess, because
> CONFIG_PPC_PREP doesn't exist anymore (at least I couldn't find it in
> "menuconfig" or in the ".config" file).
Should work, i booted 2.6.14 on my powerstack II, didn't try 2.6.15 yet, but
will this WE.
> Before trying to build a kernel myself I tried the debian linux binary
> image. An image for powerpc is not there yet so I used rc7. I netbooted
> "/boot/vmlinuz-2.6.15-rc7-powerpc" and the result was that I got a lot
> of output saying that there is something wrong. I assume the output was
> from the firmware because the kernel usually doesn't report an endless
> list of errors saying something about "stack exception" every now and
> then and mostly printing zeros followed by a new line character.
Mmm, upstream may have broken prep on 2.6.15, i have to say i didn't test it,
will have a look this WE, ok ?
> After that I copied the config from that kernel, downloaded the debian
> sources of 2.6.15, enabled ISA and some alsa ISA sound drivers and run
> into the trouble above.
Mmm, i am leaving for two days now, but i will have a look afterward.
Friendly,
Sven Luther
^ permalink raw reply
* How to build the zImage.prep was Re: Bug#345424 acknowledged by developer (Bug#345424: fixed in linux-2.6 2.6.15-1)
From: Sebastian Heutling @ 2006-01-05 10:51 UTC (permalink / raw)
To: sven.luther; +Cc: linuxppc-dev
In-Reply-To: <handler.345424.D345424.113629990832428.notifdone@bugs.debian.org>
Hi Sven,
maybe I'm just stupid - but I am not able to get an image built that can
be netbooted or put into the prep-bootloader partition. Looking at the
sources I wonder how you do it for the debian linux-images-* as the only
Makefile where it seems to generate a "zImage.prep" automagically is in
arch/ppc/boot/simple/Makefile. But that doesn't work, I guess, because
CONFIG_PPC_PREP doesn't exist anymore (at least I couldn't find it in
"menuconfig" or in the ".config" file).
Before trying to build a kernel myself I tried the debian linux binary
image. An image for powerpc is not there yet so I used rc7. I netbooted
"/boot/vmlinuz-2.6.15-rc7-powerpc" and the result was that I got a lot
of output saying that there is something wrong. I assume the output was
from the firmware because the kernel usually doesn't report an endless
list of errors saying something about "stack exception" every now and
then and mostly printing zeros followed by a new line character.
After that I copied the config from that kernel, downloaded the debian
sources of 2.6.15, enabled ISA and some alsa ISA sound drivers and run
into the trouble above.
Sebastian
Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> #345424: linux-source-2.6.14: Missing IDE IRQ for PReP Utah (PowerstackII Pro4000),
> which was filed against the linux-source-2.6.14 package.
>
> It has been closed by one of the developers, namely
> Sven Luther <luther@debian.org>.
>
> Their explanation is attached below. If this explanation is
> unsatisfactory and you have not received a better one in a separate
> message then please contact the developer, by replying to this email.
>
> Debian bug tracking system administrator
> (administrator, Debian Bugs database)
>
^ permalink raw reply
* RE: mmap
From: Fillod Stephane @ 2006-01-05 10:03 UTC (permalink / raw)
To: Brett McNerney; +Cc: linuxppc-embedded
Brett McNerney wrote:
[...]
>I am open for other options on how I can do this other then mmap. And
am still not against a driver >built into the kernel if someone has a an
example I could see and can explain how to add it in so it >builds into
the kernel since I have had no success on that either and have tried a
couple different >tutorials I found online with no success.
Ah, this is the first one of 2006. Happy new year!
Your question is a linuxppc-embedded FAQ, coming at least every 3 months
here.
It is documented in Denx's FAQ[1], and accessible through shorter
URL[2].
For more information, please follow this thread[3] (not ppc specific
actually).
A good book of C language about what are pointers and how scanf works
might=20
help too in case of confusion :-)
[1]
http://www.denx.de/twiki/bin/view/PPCEmbedded/DeviceDrivers#Section_Acce
ssingPeripheralsFromUserSpace
[2] http://tinyurl.com/6c7th
[3] http://lists.linuxppc.org/linuxppc-embedded/200403/msg00059.html
Regards,
--=20
Stephane
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox