Alex,
Follow this thread...
http://marc.info/?l=linuxppc-embedded&m=116849062702002&w=2
On Thu, 2007-05-10 at 17:45 +0100, Alex Zeffertt wrote:
> Hi list,
>
> I'm trying to port a driver from 2.6.11 to 2.6.21 and I'm stuck on the
> following line:
>
> request_irq(MPC83xx_IRQ_EXT5, mpc832
Hi list,
I'm trying to port a driver from 2.6.11 to 2.6.21 and I'm stuck on the
following line:
request_irq(MPC83xx_IRQ_EXT5, mpc832xemds_phy_interrupt, SA_SHIRQ,
"pm5384", dev);
The first problem is that MPC83xx_IRQ_EXT5 is no longer defined. If I hard
code this to
what I think is t
Hi Mirek,
I am facing the same exact problem. I am using the ML403 with standard
UART but using initramfs to generate the root file system. My root
file system contains the /dev/console node and a simple init file that
basically just tries to print out something. I can tell it is finding
my
> We are running RTC on mpc860 board with external crystal...
> We are getting 4 minutes drift for 21 hours.
A slowdown in the approx. range 1:300 to 1:350 is endemic to linux ppc:
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=157581
--
___
Linux
On May 10, 2007, at 3:57 AM, Matvejchikov Ilya wrote:
> Good Day!
>
> The command 'brctl addbr br0 eth0' brings the kernel oops if the eth0
> has PHY, but the phydev is NULL (for ex., ifconfig eth0 0.0.0.0 was
> not issued firstly)
>
> Call Trace:
> [C02CFBD0] [7FFF] 0x7fff (unreliable)
>
hi,
We are running RTC on mpc860 board with external crystal. During boot we get
date and time from h/w RTC chip and then it runs pn software tick, which is
handled by kernel. We are getting 4 minutes drift for 21 hours. Can any one
suggest, how to reduce the drift.
thnax in advance,
pjmaiya_
Hi,
For the record, I've just merged powerpc.git from kernel.org and it has started
working now! Clearly this means it was a kernel issue rather than a bootloader
issue.
Regards,
Alex
Alex Zeffertt wrote:
> Hi,
>
> Sorry about the cross posting, but I'm not sure which list I should send
> to
Good Day!
The command 'brctl addbr br0 eth0' brings the kernel oops if the eth0
has PHY, but the phydev is NULL (for ex., ifconfig eth0 0.0.0.0 was
not issued firstly)
Call Trace:
[C02CFBD0] [7FFF] 0x7fff (unreliable)
[C02CFBE0] [C0109634] dev_ethtool+0x1b0/0xfac
[C02CFCD0] [C0155EF0] por
Thank you for all of the advices.
I did more study on that problem but still without the success.
1. I did redd the ELDK manual and I have invoked :
ELDK_FIXOWNER
ELDK_MAKEDEV
in the "dev" directory there were created many nodes like that:
crw-rw-rw-1 root root 5, 1 May 8 15:42
