madwifi

madwifi

[Andrew Paulsen]

Does anyone have any tips for including madwifi into a gpe-image build?

I can "bitbake madwifi-ng" by itself and that appears to work.

If I add
BOOTSTRAP_EXTRA_RDEPENDS = "madwifi-ng"
to my machine.conf, or add

GPE_EXTRA_INSTALL += "madwifi-ng"
to my gpe-image.bb, I get an:

"ERROR: Nothing provides runtime dependency madwifi-ng"

Is there a better way to add packages to an image?

Re: madwifi

[Justin Patrin]

On 12/4/06, Andrew Paulsen <andrew.paulsen@gmail.com> wrote:
> Does anyone have any tips for including madwifi into a gpe-image build?
>
> I can "bitbake madwifi-ng" by itself and that appears to work.
>
> If I add
> BOOTSTRAP_EXTRA_RDEPENDS = "madwifi-ng"
> to my machine.conf, or add
>
> GPE_EXTRA_INSTALL += "madwifi-ng"
> to my gpe-image.bb, I get an:
>
> "ERROR: Nothing provides runtime dependency madwifi-ng"
>
> Is there a better way to add packages to an image?
>

The problem you're facing is that you're adding only a runtime
(install-time) dependency and not a compile-time dependency. If you're
compiling in the .dev branch then this is likely a bug (if you're
using BOOTSTRAP_EXTRA_RDEPENDS). If you're using the .oz354x branch
then you need to add madwifi-ng to the DEPENDS of the file you're
editing too.

-- 
Justin Patrin

Re: madwifi

[Andrew Paulsen]

On 12/5/06, Justin Patrin <papercrane@gmail.com> wrote:
> On 12/4/06, Andrew Paulsen <andrew.paulsen@gmail.com> wrote:
> > Does anyone have any tips for including madwifi into a gpe-image build?
> >
> > I can "bitbake madwifi-ng" by itself and that appears to work.
> >
> > If I add
> > BOOTSTRAP_EXTRA_RDEPENDS = "madwifi-ng"
> > to my machine.conf, or add
> >
> > GPE_EXTRA_INSTALL += "madwifi-ng"
> > to my gpe-image.bb, I get an:
> >
> > "ERROR: Nothing provides runtime dependency madwifi-ng"
> >
> > Is there a better way to add packages to an image?
> >
>
> The problem you're facing is that you're adding only a runtime
> (install-time) dependency and not a compile-time dependency. If you're
> compiling in the .dev branch then this is likely a bug (if you're
> using BOOTSTRAP_EXTRA_RDEPENDS). If you're using the .oz354x branch
> then you need to add madwifi-ng to the DEPENDS of the file you're
> editing too.
>
> --
> Justin Patrin

Ok, I tried a few more things this morning, but I'm still getting
errors.  Here's what I'm working with:

OE Build Configuration:
BB_VERSION     = "1.6.3"
OE_REVISION    = "dbe2d7e445c33fd9403d6edaf6ec36d1857ada98"
TARGET_ARCH    = "arm"
TARGET_OS      = "linux"
MACHINE        = "compulab-pxa270"
DISTRO         = "generic"
DISTRO_VERSION = ".dev-snapshot-20061205"
TARGET_FPU     = "soft"
I am using the .oz354x branch of OE.

I first tried adding the following to my machine.conf file:
BOOTSTRAP_EXTRA_RDEPENDS = "madwifi-ng"
DEPENDS += "madwifi-ng"

Which promptly broke my build with a circular dependency:
ERROR: /stuff/org.openembedded.dev/packages/quilt/quilt-native_0.45.bb
depends on itself (eventually)
ERROR: upwards chain is: gpe-image (gpe-image) -> ipkg-native
(ipkg-native) -> pkgconfig-native (pkgconfig-native) ->
autoconf-native (autoconf-native) -> quilt-native (quilt-native) ->
madwifi-ng (madwifi-ng) -> ipkg-utils-native (ipkg-utils-native)

I then tried adding the following to my gpe-image.bb file:
GPE_EXTRA_INSTALL += "madwifi-ng"
DEPENDS += "madwifi-ng"

I also tried a few combinations of adding madwifi-ng to
GPE_EXTRA_INSTALL, DEPENDS, and RDEPENDS to gpe-image.bb to see if
dumb luck would help ... it didn't.

Other than the circular dependency error, I always get:
ERROR: Nothing provides runtime dependency madwifi-ng

Re: madwifi

[Robert Wörle]

Dear Andrew

Is there a specific reason why you work with the .oz354 tree ?
This tree is old and i think not maintained anymore ,, ( people correct
me if am wrong )

Also that you miss tmp/work/ARCHITECURE directory tells me that you
should consider a
mtn update in order to sync your tree to the current state .. then
please use .dev tree .

btw : how is your compulab ?  we also evaluate it here and i am getting
good results also using the current .dev tree

rob_w
> Ok, I tried a few more things this morning, but I'm still getting
> errors.  Here's what I'm working with:
>
> OE Build Configuration:
> BB_VERSION     = "1.6.3"
> OE_REVISION    = "dbe2d7e445c33fd9403d6edaf6ec36d1857ada98"
> TARGET_ARCH    = "arm"
> TARGET_OS      = "linux"
> MACHINE        = "compulab-pxa270"
> DISTRO         = "generic"
> DISTRO_VERSION = ".dev-snapshot-20061205"
> TARGET_FPU     = "soft"
> I am using the .oz354x branch of OE.
>
> I first tried adding the following to my machine.conf file:
> BOOTSTRAP_EXTRA_RDEPENDS = "madwifi-ng"
> DEPENDS += "madwifi-ng"
>
> Which promptly broke my build with a circular dependency:
> ERROR: /stuff/org.openembedded.dev/packages/quilt/quilt-native_0.45.bb
> depends on itself (eventually)
> ERROR: upwards chain is: gpe-image (gpe-image) -> ipkg-native
> (ipkg-native) -> pkgconfig-native (pkgconfig-native) ->
> autoconf-native (autoconf-native) -> quilt-native (quilt-native) ->
> madwifi-ng (madwifi-ng) -> ipkg-utils-native (ipkg-utils-native)
>
> I then tried adding the following to my gpe-image.bb file:
> GPE_EXTRA_INSTALL += "madwifi-ng"
> DEPENDS += "madwifi-ng"
>
> I also tried a few combinations of adding madwifi-ng to
> GPE_EXTRA_INSTALL, DEPENDS, and RDEPENDS to gpe-image.bb to see if
> dumb luck would help ... it didn't.
>
> Other than the circular dependency error, I always get:
> ERROR: Nothing provides runtime dependency madwifi-ng
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
>   

Re: madwifi

[Marcin Juszkiewicz]

Dnia wtorek, 5 grudnia 2006 16:02, Robert Wörle napisał:

> Is there a specific reason why you work with the .oz354 tree ?
> This tree is old and i think not maintained anymore ,, ( people correct
> me if am wrong )

Tree is maintained but have very small amount of changes. It should not be 
used for non-OpenZaurus supported machines anyway.

I suggest using .dev for any development. .oz354x tree is used to maintain 
OpenZaurus updates.

-- 
JID: hrw-jabber.org
OpenEmbedded developer/consultant

            That must be wonderful! I don understand it at all.

Re: madwifi

[Andrew Paulsen]

On 12/5/06, Robert Wörle <robert@linuxdevelopment.de> wrote:
> Dear Andrew
>
> Is there a specific reason why you work with the .oz354 tree ?
> This tree is old and i think not maintained anymore ,, ( people correct
> me if am wrong )
>
> Also that you miss tmp/work/ARCHITECURE directory tells me that you
> should consider a
> mtn update in order to sync your tree to the current state .. then
> please use .dev tree .
>
> btw : how is your compulab ?  we also evaluate it here and i am getting
> good results also using the current .dev tree

Our Compulab board is working very well so far, I just got the LCD up
and running yesterday and I'll add a touch screen today.  And
hopefully wifi support :)

I am NOT using .oz354, I am using org.openembedded.dev, sorry for the mistake.

madwifi

[Ronald G. Minnich]

well, on 2.6.10, I did trace down pci_map_single, which is what the ath 
driver uses for setting up the RX and TX descriptors. 

I will be looking and testing some more, but it looks like bus_map_single 
on 2.6.10 uses virt_to_phys, which looks wrong to me. I think it should be 
using virt_to_bus. This would explain why the atheros packets splatter all 
over memory instead of going to the correct place. More as I find it.

ron


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click