From: Michael Buesch <mb@bu3sch.de>
To: Pavel Roskin <proski@gnu.org>
Cc: bcm43xx-dev@lists.berlios.de, netdev@vger.kernel.org
Subject: Re: What is in bcm43xx-wireless-dev.git?
Date: Sat, 13 Jan 2007 15:09:26 +0100 [thread overview]
Message-ID: <200701131509.26877.mb@bu3sch.de> (raw)
In-Reply-To: <20070113024543.aj2n40s4k0g0cgws@webmail.spamcop.net>
On Saturday 13 January 2007 08:45, Pavel Roskin wrote:
> Quoting Michael Buesch <mb@bu3sch.de>:
>
> > > drivers/ssb/driver_mips/mips.c includes asm/time.h, which is missing on
> > > x86_64. It also refers to struct ssb_serial_ports, which is not defined
> > > anywhere.
> >
> > Yeah, CONFIG_SSB_MIPS should depend on the MIPS CPU.
> > Which kconfig option do you suggest to make a "depend" on?
>
> I try not to add artificial restrictions. The driver should depend on the
> components providing the necessary API.
Ehm, it is clearly not artificial. The MIPS core depends on the MIPS
platform. Logically and technically. You must not enable it on
non-MIPS platforms, as it's tied with the internals of the MIPS
arch dependent code.
The only logical way to solve the compile issues are to make a dependency
on the MIPS platform.
> > > drivers/ssb/driver_pci/pcicore.c refers to SSB_PCICORE_SBTOPCI1_CFG1
> > > that is not defined anywhere in the kernel.
> >
> > Yeah, could be a typo. I'll have a look at it.
>
> I only found it because the driver didn't depend on MIPS. See what I mean?
>
> This only manifests if CONFIG_SSB_PCICORE_HOSTMODE is defined, and it is only
> selected by CONFIG_SSB_DRIVER_MIPS.
HOSTMODE is not really tested, yet.
And HOSTMODE is _also_ very closely tied to the MIPS platform. So
it must depend on it, too (probably indirectly through the MIPS core driver).
To be honest, I did not even compiletest the HOSTMODE code, as I don't
even have a device for it. But I am going to fix that before pushing stuff
upstream.
> > Hm, not sure why this oopses. It works on PPC (can transmit data and so on).
>
> My PPC machine is a venerable Blue&White G3, so it won't take PCIe.
I looked more closely at it, but I really can't see why it oopses.
Any idea what's happening there?
> > Does it work with linville's tree (in DMA mode)?
>
> Yes, it does. I couldn't connect to the AP, but it's a different story. I may
> be doing things wrong. At least I can scan and I see the APs around.
Well, ok. So it should work in my tree, too, once we fixed the DMA oops.
--
Greetings Michael.
next prev parent reply other threads:[~2007-01-13 14:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-13 7:45 What is in bcm43xx-wireless-dev.git? Pavel Roskin
2007-01-13 14:09 ` Michael Buesch [this message]
2007-01-13 19:30 ` Pavel Roskin
[not found] ` <20070113143033.fi804so8ok04wc4k-2RFepEojUI3Rd1RZctBqVdHuzzzSOjJt@public.gmane.org>
2007-01-13 19:51 ` Michael Buesch
2007-01-14 2:10 ` Pavel Roskin
[not found] ` <20070113211030.11zo8cokcsoskccg-2RFepEojUI3Rd1RZctBqVdHuzzzSOjJt@public.gmane.org>
2007-01-14 10:15 ` Michael Buesch
2007-01-14 14:18 ` Pavel Roskin
[not found] ` <20070114091812.hz2fokosw0o0cc0k-2RFepEojUI3Rd1RZctBqVdHuzzzSOjJt@public.gmane.org>
2007-01-14 15:51 ` Michael Buesch
2007-01-14 16:39 ` Pavel Roskin
[not found] ` <20070114113910.py9s0gggk8gwskwo-2RFepEojUI3Rd1RZctBqVdHuzzzSOjJt@public.gmane.org>
2007-01-14 17:21 ` Michael Buesch
-- strict thread matches above, loose matches on Subject: below --
2007-01-11 20:10 Michael Buesch
2007-01-12 7:25 ` Pavel Roskin
2007-01-12 14:06 ` Michael Buesch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200701131509.26877.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=netdev@vger.kernel.org \
--cc=proski@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).