From: Marcin Juszkiewicz <openembedded@hrw.one.pl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] madwifi staging and hostap-deamon support for madwifi
Date: Mon, 12 Mar 2007 09:08:43 +0100 [thread overview]
Message-ID: <200703120908.45917.openembedded@hrw.one.pl> (raw)
In-Reply-To: <45F4C45B.8020601@whitby.id.au>
Dnia poniedziałek, 12 marca 2007, Rod Whitby napisał:
> I want to get hostap-deamon working for madwifi (on the IOMega NAS100d,
> and D-Link DSMG-600 RevA).
And also on any other PCI equipped machines (madwifi req pci iirc).
> Currently, it does not support madwifi, and the current madwifi-ng
> recipe is putting the include files in a place other than the place
> that hostapd looks for them during the compile.
> Also, hostapd has an RDEPENDS on hostapd-modules, which does not make
> sense for madwifi.
Hostap-modules dependency should be dropped - we use hostap from kernel.
I would like to get latest stable hostapd in OE.
> I'd like to change madwifi-ng to put the files in the right place, and
> then change hostap-daemon to enable madwifi support and use those
> include files. Are there any other known packages that use madwifi
> include files that may be affected?
wpa-supplicant use madwifi and also has all needed code for madwifi
support on PCI equipped machines.
> I can either enable this globally, or enable it for the slugos distro
> only, or enable it for ixp4xx machines only. Which should I do?
Enable it for PCI equipped machines like it is in wpa-supplicant 0.5.x
> Here is the hostap-daemon.inc patch (example using a _ixp4xx override):
> > -RDEPENDS = "hostap-modules hostap-utils (${PV})"
> > +RDEPENDS = "hostap-utils (${PV})"
> > +DEPENDS_append_ixp4xx = " madwifi-ng"
> >
> > +do_configure_ixp4xx() {
> > + sed -e
> > 's/\#CONFIG_DRIVER_MADWIFI=y/CONFIG_DRIVER_MADWIFI=y/' \ +
> > '${WORKDIR}/defconfig' >>'${S}/.config'
> > +}
Do this like it is done in wpa-supplicant 0.5.x
Thx
--
JID: hrw-jabber.org
OpenEmbedded developer/consultant
Truly a man of few words. I'll bet you don't know what either one of them
means.
prev parent reply other threads:[~2007-03-12 8:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-12 3:09 [RFC] madwifi staging and hostap-deamon support for madwifi Rod Whitby
2007-03-12 8:08 ` Marcin Juszkiewicz [this message]
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=200703120908.45917.openembedded@hrw.one.pl \
--to=openembedded@hrw.one.pl \
--cc=openembedded-devel@lists.openembedded.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