linuxppc-embedded help needed:kernel access of bad area

2005-12-01 Thread [EMAIL PROTECTED]
7DE0 0014 C01A5AC0 GPR08: 0450 000C C01A 30025CE8 10018B5C GPR16: 9032 006B1F40 C0003E88 GPR24: C0003BE0 0001 1500 7EA4 7DE0 FFEA C01A5AA0 0014 Call backtrace: 1A1C C003A310

linuxppc-embedded help needed:kernel access of bad area

2005-12-01 Thread Rune Torgersen
> -Original Message- > From: zengshuai at sogou.com > Sent: Thursday, December 01, 2005 00:52 > #define BCSRADDR 0x0450 This address is wrong. It's the address the manual gives, but the bootloadre usually moves it because it interferes with the SDRAM when running Linux. Check the bootl

AW: RE: linuxppc-embedded help needed:kernel access of bad area

2005-12-01 Thread Achim Machura
Hello, > #define BCSRADDR 0x0450 > ... > static int PQ2FADS_GPL_open(struct inode *inode,struct file *filp) > { > PQ2FADS_GPL_CSR=(PQ2FADS_BCSR*)BCSRADDR; possible you have to change physical address to logical see ioremap. achim

linuxppc-embedded help needed:kernel access of bad area

2005-11-30 Thread [EMAIL PROTECTED]
tion fault # -- > --- > From: zengshuai at sogou.com > To: ppc > Subject: linuxppc-embedded help needed:kernel access of bad area > Sent: Wed Nov 30 16:18:06 CST 2005 > > > i writed a led driver for PQ2

linuxppc-embedded help needed:kernel access of bad area

2005-11-30 Thread [EMAIL PROTECTED]
i writed a led driver for PQ2FADS(a ppc board). but i can't read/write 0x0450 where led register addr locate in. i tested two ways to do that. first, p=0x0450; *p=0x12; second, outb(0x12,0x0450); ... two ways both didn't work.they had a some wrong:kernel access of bad area. how can

linuxppc-embedded help needed:kernel access of bad area

2005-11-30 Thread Fillod Stephane
Dear zengshuai, zengshuai at sogou.com wrote: > i writed a led driver for PQ2FADS(a ppc board). > but i can't read/write 0x0450 where led register addr locate in. > i tested two ways to do that. > first, > p=0x0450; > *p=0x12; > > second, > outb(0x12,0x0450); > ... > two ways both