Does anybody know of a "linux-wireless" list somewhere?
On Sun, Apr 11, 2004 at 12:39:03PM -0600, Mike Wellington wrote: ... If you check marc.theaimsgroup.com and search for wlan a copule will turn up. Did you try google first? Sam ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
kfree_skb on hard IRQ ???
Steven Scholz wrote: > > Hi there, > > my HERMES-II drivers causes a lot of > > Warning: kfree_skb on hard IRQ c38c2168 > > messages. > > What do they mean? And what means alloc_skb called nonatomically from interrupt c00eb8d0 kernel BUG at skbuff.c:174! Oops: Kernel Mode Software FPU Emulation, sig: 8 NIP: C00E065C XER: LR: C00E065C SP: C016BC80 REGS: c016bbd0 TRAP: 1000Not tainted MSR: 1032 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 11 TASK = c0169fa0[0] 'swapper' Last syscall: 120 last math last altivec ... Kernel panic: Aiee, killing interrupt handler! In interrupt handler - not syncing <0>Rebooting in 10 seconds.. ??? Thanks a million! -- Steven Scholz imc Measurement & Control imc Me?systeme GmbH Voltastr. 5 Voltastr. 5 13355 Berlin13355 Berlin Germany Deutschland ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
kfree_skb on hard IRQ ???
Steven Scholz wrote: > > Hi there, > > my HERMES-II drivers causes a lot of > > Warning: kfree_skb on hard IRQ c38c2168 > > messages. > > What do they mean? Is it enough to just replace dev_kfree_skb() with dev_kfree_skb_irq() ??? Thanks, Steven ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
kfree_skb on hard IRQ ???
Hi there, my HERMES-II drivers causes a lot of Warning: kfree_skb on hard IRQ c38c2168 messages. What do they mean? A grep on kernel sources brought me drivers/net/smc9.c: . 12/15/00 Christian Jullien fix "Warning: kfree_skb on hard IRQ" drivers/net/smc9194.c: . 12/15/00 Christian Jullien fix "Warning: kfree_skb on hard IRQ" drivers/net/hamradio/yam.c: * OK1ZIA 2.09.01 Fixed "kfree_skb on hard IRQ" net/core/skbuff.c: printk(KERN_WARNING "Warning: kfree_skb on hard IRQ %p\n", but I don't know how they fixed that... Thanks! -- Steven Scholz imc Measurement & Control imc Me?systeme GmbH Voltastr. 5 Voltastr. 5 13355 Berlin13355 Berlin Germany Deutschland ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
machine checks with MPC107 and read_config?
Andrew Klossner wrote: >I'm bringing up 2.6 on some embedded boards using G3/G4 CPUs and an >MPC107. We've been running vxWorks on these boards for years and we >know the chips pretty well. > >During startup, the first attempt to read the config space from an >unpopulated devfn causes an oops: machine check. > Do you have the bridge's regs mapped into virtual memory? Use an existing platform that uses the mpc107 like the sandpoint as an example. Pay special attention to the use of the 'set_bat' and 'io_block_mapping' routines. >Looking at arch/ppc/syslib/indirect_pci.c, I see the fundamental >read-config operation, but I don't see it bracketed by writes to >MPC107 registers to temporarily disable master-abort error enable. >Specifically, I would expect bit 1 "PCI master-abort error enable" to >be turned off in register 0xc0 "Error enabling register 1", then >restored at the end of the routine, and I would expect to see a test >of bit 13 "received master-abort" in register 0x06 "PCI status >register" to see whether the config-space access succeeded. > You are correct. The mpc10x_common.c code is basic and more concerned with getting the bridge to use the proper address map than anything else. The level of detection and, presumably, handling just isn't there. If you need it, I'm afraid you're going to have to implement it. >Before I sidestep the code in mpc10x_common.c and indirect_pci.c, let >me ask: does everybody else run with master-abort detection turned >off? > Maybe the MAC guys worry about it but AFAIK, most other platforms don't. > Doesn't that hurt your ability to find bad pointers into >I/O space? > Maybe but you're probably going to notice other symptoms of bad I/O space pointers anyway, so is it worth it? > Or am I overlooking something here? Maybe I am? Mark ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
problem with queue_task() and mark_bh()...
Hi there,
I have a problem with queue_task() and mark_bh().
In a driver for the wireless HERMES-II chipset I found the code snippets
/* Register the ISR handler information here... */
lp->task.routine = (void (*)(void *))wl_isr_handler;
lp->task.data = lp;
printk("wl_isr_handler is @ %#lx\n", lp->task.routine);
At a later point (namely in the interrupt service rountine this happens:
/* If we have interrupts pending, then put them on a system task queue.*/
if( events == HCF_INT_PENDING ) {
/* Schedule the ISR handler as a bottom-half task in the
* tq_immediate queue
*/
printk( "Schedule the ISR handler %#lx...\n", lp->task.routine);
queue_task( &( lp->task ), &tq_immediate );
mark_bh( IMMEDIATE_BH );
}
The problem is now that the queued task lp->task (i.e. wl_isr_handler) never
get's called! And thus the driver does not work.
If I call the function directly using
lp->task.routine(lp);
instead of queue_task() and mark_bh() the function wl_isr_handler() gets
called and the driver works.
Any idea why queue_task() and mark_bh() do not work as expected?
How could I debug this problem?
(The two printk's show the same address.)
I am using linuxppc-2.4.25 from DENX CVS.
Thanks a million!!!
--
Steven Scholz
imc Measurement & Control imc Me?systeme GmbH
Voltastr. 5 Voltastr. 5
13355 Berlin13355 Berlin
Germany Deutschland
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
machine checks with MPC107 and read_config?
I'm bringing up 2.6 on some embedded boards using G3/G4 CPUs and an MPC107. We've been running vxWorks on these boards for years and we know the chips pretty well. During startup, the first attempt to read the config space from an unpopulated devfn causes an oops: machine check. Looking at arch/ppc/syslib/indirect_pci.c, I see the fundamental read-config operation, but I don't see it bracketed by writes to MPC107 registers to temporarily disable master-abort error enable. Specifically, I would expect bit 1 "PCI master-abort error enable" to be turned off in register 0xc0 "Error enabling register 1", then restored at the end of the routine, and I would expect to see a test of bit 13 "received master-abort" in register 0x06 "PCI status register" to see whether the config-space access succeeded. Before I sidestep the code in mpc10x_common.c and indirect_pci.c, let me ask: does everybody else run with master-abort detection turned off? Doesn't that hurt your ability to find bad pointers into I/O space? Or am I overlooking something here? Thanks, Andrew Klossner ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Xilinx ML300 u-boot question
Peter- That solves part of the problem. I'd still have to either download a new u-boot via XPS or copy it to the MicroDrive every time I changed u-boot. I'll do it this way for now, but it would be better if I built two different u-boots that are made to execute from different RAM locations. Then I can download the (changeable) second-stage u-boot via tftp. -mike wellington wellington at lucent.com platform at bithead.com Peter Ryser wrote: > > Mike, > > for TFTP boot normally the HW MAC address of the target device is used > for identification. On the ML300 the HW MAC address is stored inside the > IIC EEPROM. Since accessing this EEPROM is not yet supported in the > pusblished U-Boot port for ML300 the MAC address is hardcoded in > board/xilinx/xilinx_enet/emac_adapter.c. > > So, to get a machine specific u-boot for every board change the MAC > address and recompile. I'm not sure that you would need the secondary > u-boot then as you could then directly load the Linux kernel in the > second step. > > - Peter > > > Mike Wellington wrote: > >> >> Does anybody know what parameters I should use to >> load u-boot, using u-boot.That's right, I want to >> build a generic u-boot that goes on the Microdrive of >> a Xilinx ML300 development board. I have several of them >> to manage. I want the generic u-boot to go and download >> a machine-specific u-boot that I can change on my workstation >> without having to write it to the microdrive. >> >> Or can I just have u-boot start the kernel with no parameters >> and have all the initial args for the kernel built into the >> kernel? >> >> -mike wellington >> wellington at lucent.com >> >> >> >> > > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Xilinx ML300 u-boot question
Gerald (et al) - 1) kernel configuration - tried changing the default kernel command line, but that didn't work. The kernel started up, but did not set its "ip=" parameters as I specified. This method would work fine, but I'd prefer to not have to keep a separate kernel around for each machine. 2) conditional execution commands from u-boot - this sounds like a good option, I don't know anything about these commands. I guess I can distiguish one from another via the IP address. I'll persue this. And thanks for saving me from wasting my time trying to make a RAM only u-boot. -mike wellington wellington at lucent.com platforms at bithead.com VanBaren, Gerald (AGRE) wrote: > You can build custom kernels with built-in values instead of using the boot > line to set the values. That would be simpler than chaining u-boot because > u-boot expects a bare machine on start up. To chain u-boot, you basically > would have to make a "run from RAM" u-boot -- while not impossible, it takes > time and effort and isn't a supported configuration (i.e. Wolfgang won't > answer your questions in his usual thorough manner ;-). > > You should be able to use the command language built into u-boot to select > linux bootline parameters. You must be able to detect differences in the > target systems in order to load a custom u-boot or linux -- why not use that > with the u-boot conditional commands to select or build up the proper linux > bootline? > > gvb > > > >>-Original Message- >>From: owner-linuxppc-embedded at lists.linuxppc.org >>[mailto:owner-linuxppc-embedded at lists.linuxppc.org]On Behalf Of Mike >>Wellington >>Sent: Tuesday, April 13, 2004 11:29 AM >>To: linuxppc-embedded at lists.linuxppc.org >>Subject: Xilinx ML300 u-boot question >> >> >> >>Does anybody know what parameters I should use to >>load u-boot, using u-boot.That's right, I want to >>build a generic u-boot that goes on the Microdrive of >>a Xilinx ML300 development board. I have several of them >>to manage. I want the generic u-boot to go and download >>a machine-specific u-boot that I can change on my workstation >>without having to write it to the microdrive. >> >>Or can I just have u-boot start the kernel with no parameters >>and have all the initial args for the kernel built into the >>kernel? >> >>-mike wellington >> wellington at lucent.com >> >> > > > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
System ACE MPU interface to CF card
Sharad Gupta sharad-at-buckeye.ece.drexel.edu |PPC Linux Embedded| wrote: > Can you send me your board patch so that I can configure and build ACE > driver for my board ? I want some help in knowing how and where to > customize the driver for one's board. The attached patch demonstrates how I enabled the SYSACE driver for my (JSE) board. I'm not so sure I'm happy with it, because each board will have to do something similar. I'm thinking that the CONFIG_XILINX_SYSACE define should lose its dependence on CONFIG_XILINX_OCP, but I'm not clear on the best way to account for this in the xilinx_ocp/Makefile. NOTE: This patch is meant to demonstrate my thinking on this matter. It's not complete. -- Steve Williams"The woods are lovely, dark and deep. steve at XX But I have promises to keep, http://www.XX and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep." -- next part -- An embedded and charset-unspecified text was scrubbed... Name: foo.txt Url: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20040413/e06011be/attachment.txt
Xilinx ML300 u-boot question
Mike, for TFTP boot normally the HW MAC address of the target device is used for identification. On the ML300 the HW MAC address is stored inside the IIC EEPROM. Since accessing this EEPROM is not yet supported in the pusblished U-Boot port for ML300 the MAC address is hardcoded in board/xilinx/xilinx_enet/emac_adapter.c. So, to get a machine specific u-boot for every board change the MAC address and recompile. I'm not sure that you would need the secondary u-boot then as you could then directly load the Linux kernel in the second step. - Peter Mike Wellington wrote: > > Does anybody know what parameters I should use to > load u-boot, using u-boot.That's right, I want to > build a generic u-boot that goes on the Microdrive of > a Xilinx ML300 development board. I have several of them > to manage. I want the generic u-boot to go and download > a machine-specific u-boot that I can change on my workstation > without having to write it to the microdrive. > > Or can I just have u-boot start the kernel with no parameters > and have all the initial args for the kernel built into the > kernel? > > -mike wellington > wellington at lucent.com > > > > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Xilinx ML300 u-boot question
You can build custom kernels with built-in values instead of using the boot line to set the values. That would be simpler than chaining u-boot because u-boot expects a bare machine on start up. To chain u-boot, you basically would have to make a "run from RAM" u-boot -- while not impossible, it takes time and effort and isn't a supported configuration (i.e. Wolfgang won't answer your questions in his usual thorough manner ;-). You should be able to use the command language built into u-boot to select linux bootline parameters. You must be able to detect differences in the target systems in order to load a custom u-boot or linux -- why not use that with the u-boot conditional commands to select or build up the proper linux bootline? gvb > -Original Message- > From: owner-linuxppc-embedded at lists.linuxppc.org > [mailto:owner-linuxppc-embedded at lists.linuxppc.org]On Behalf Of Mike > Wellington > Sent: Tuesday, April 13, 2004 11:29 AM > To: linuxppc-embedded at lists.linuxppc.org > Subject: Xilinx ML300 u-boot question > > > > Does anybody know what parameters I should use to > load u-boot, using u-boot.That's right, I want to > build a generic u-boot that goes on the Microdrive of > a Xilinx ML300 development board. I have several of them > to manage. I want the generic u-boot to go and download > a machine-specific u-boot that I can change on my workstation > without having to write it to the microdrive. > > Or can I just have u-boot start the kernel with no parameters > and have all the initial args for the kernel built into the > kernel? > > -mike wellington > wellington at lucent.com > > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Xilinx ML300 u-boot question
Does anybody know what parameters I should use to load u-boot, using u-boot.That's right, I want to build a generic u-boot that goes on the Microdrive of a Xilinx ML300 development board. I have several of them to manage. I want the generic u-boot to go and download a machine-specific u-boot that I can change on my workstation without having to write it to the microdrive. Or can I just have u-boot start the kernel with no parameters and have all the initial args for the kernel built into the kernel? -mike wellington wellington at lucent.com ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
