I'm working on getting a 2.6 kernel and PCMCIA working on a Linksys
WRT54G3G (mips) and having a few issues with their bus implementation.
Specifically, when yenta_socket tries to disable interrupts by
writing 0x0 to CB_SOCKET_MASK or check if they're enabled by reading
from I365_INTCTL (ti_init i
Hi,
January 2008 there was a thread on integration support for PCMCIA on
MIPS, specifically the Linksys WRT54G3G. The cardbus is implemented by a
TI1510 on a Broadcom 47xx. Linksys' patches based on 2.4.20. Has anyone
made some progress in supporting this platform?
Dirk
_
On Fri, Jan 18, 2008 at 12:28:23PM -0700, RB wrote:
> Specifically, when yenta_socket tries to disable interrupts by
> writing 0x0 to CB_SOCKET_MASK or check if they're enabled by
> reading from I365_INTCTL (ti_init in ti113x.h), the driver loading
> fails with a data bus error and there's a result
> This is tough to debug.
Yeah... I figured that out the hard way. Nothing like intro to driver
development by fire.
> What does the oops look like?
Here's one from the crash induced by reading I365_INTCTL; I don't have
the rest immediately available, but this thread has most of what I've
posted
On Fri, Jan 18, 2008 at 07:31:03PM -0700, RB wrote:
> > What does the oops look like?
> Here's one from the crash induced by reading I365_INTCTL;
Symbol names would help. But I think you should find MIPS experts
who can help you sort out the low level problem. Try linux-mips or
simply lkml for a g
I've been using ksymoops to decode these, but am enough of a newb on
this to not know whether my x86-only ksymoops is able to do so
properly, even with the modules/System.map/vmlinux/etc.
I'll start poking around toward linux-mips or the general list. I
think it's a buggy implementation by Linksy
Nothing, I didn't pursue it any further but would glad to help debug.
On Mon, Jan 19, 2009 at 13:14, Dirk Nehring wrote:
> Hi,
>
> January 2008 there was a thread on integration support for PCMCIA on
> MIPS, specifically the Linksys WRT54G3G. The cardbus is implemented by a
> TI1510 on a Broadcom