From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH resend] owl-linux: new package
Date: Tue, 26 Jun 2012 10:37:29 +0200 [thread overview]
Message-ID: <20120626103729.4b0fbffd@skate> (raw)
In-Reply-To: <CAHt8ZCOE0ZfTQh2kw54YCEhS3tUSUSGVP9dAoQc8K31r2=4wyg@mail.gmail.com>
Le Tue, 26 Jun 2012 09:07:46 +0100,
Simon Dawson <spdawson@gmail.com> a ?crit :
> > Maybe group the ARM9 and EABI checks into one comment? And maybe make
> > it visible only on ARM?
> >
> > comment "owl-linux is only supported on ARM9 architecture with EABI"
> > ? ? ? ?depends on !(BR2_arm920t || BR2_arm922t || BR2_arm926t) || !BR2_ARM_EABI
> > ? ? ? ?depends on BR2_arm
> >
> > or something like that.
>
> Good idea; I will do this.
Thanks!
> > At some point in the discussion, it was mentioned that this driver
> > might only work with one particular CodeSourcery toolchain, which would
> > suggest that it uses the C library, and therefore contain userspace
> > code. But here you're only installing the kernel module itself. Could
> > you clarify this point, just for our (my?) knowledge?
>
> I'm using the Buildroot-generated uClibc-based toolchain, and have had
> no problems so far. The kernel module installed by this package is all
> that is required to make the H&D Wireless hardware work.
Ok, if there's only kernel code, then I guess the only problem is the
ABI, which you've already handled by requiring EABI, so that looks good.
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-06-26 8:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-25 19:09 [Buildroot] [PATCH resend] owl-linux: new package spdawson at gmail.com
2012-06-26 7:35 ` Thomas Petazzoni
2012-06-26 8:07 ` Simon Dawson
2012-06-26 8:37 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-06-05 6:47 spdawson at gmail.com
2012-05-25 21:07 spdawson at gmail.com
2012-06-04 23:16 ` Arnout Vandecappelle
2012-06-05 6:36 ` Simon Dawson
2012-05-25 12:51 spdawson at gmail.com
2012-05-25 20:08 ` Peter Korsgaard
[not found] ` <CAC1BbcRi_0KzkKP7Pfi6e407kp3QGyiWj+mVEA355z_HeC1qvg@mail.gmail.com>
2012-05-25 20:33 ` Bernhard Reutner-Fischer
2012-05-25 21:01 ` Simon Dawson
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=20120626103729.4b0fbffd@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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