From: Jonas Bonn <jonas@southpole.se>
To: Richard Weinberger <richard@nod.at>
Cc: arnd@arndb.de, linux@openrisc.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] OpenRISC: IRQ: Include module.h
Date: Wed, 29 Feb 2012 09:56:14 +0100 [thread overview]
Message-ID: <1330505774.2964.31.camel@crucifix> (raw)
In-Reply-To: <4F4DE438.6050707@nod.at>
On Wed, 2012-02-29 at 09:39 +0100, Richard Weinberger wrote:
> Am 29.02.2012 08:49, schrieb Jonas Bonn:
> You are right. export.h is better.
> I forgot commit f501693 (module.h: split out the EXPORT_SYMBOL into export.h).
>
> > Thanks for helping out with build-testing the OpenRISC arch... much
> > appreciated.
>
> I'm doing more than build-testing.
> Yesterday my FPGA board booted the very first time Linux on OpenRISC. :-)
>
> Thanks,
> //richard
>
Ah, awesome! Glad to hear that.
I'll just let you in on the little catch with the upstream OpenRISC
kernel, then: it drops support for deprecated syscalls; unfortunately,
there is no libc that supports that yet.
For that reason, the kernel at git://openrisc.net/jonas/linux is still
the one that is most usable... it's carrying a patch to reenable those
syscalls so that uClibc works.
I've got a patch series that attempts to fix that, but upstream uClibc
didn't seem particularly enamored by the idea of adding more code to
libc so that Linux can get smaller... and that's kind of where we got
stuck.
Probably best to drop linux-kernel from this conversation at this point,
but feel free to continue it at linux@lists.openrisc.net
/Jonas
next prev parent reply other threads:[~2012-02-29 8:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 0:46 [PATCH 1/2] OpenRISC: Fix audit_syscall_exit() usage Richard Weinberger
2012-02-29 0:46 ` [PATCH 2/2] OpenRISC: IRQ: Include module.h Richard Weinberger
2012-02-29 7:49 ` Jonas Bonn
2012-02-29 8:39 ` Richard Weinberger
2012-02-29 8:56 ` Jonas Bonn [this message]
2012-02-29 7:46 ` [PATCH 1/2] OpenRISC: Fix audit_syscall_exit() usage Jonas Bonn
2012-02-29 8:34 ` Richard Weinberger
2012-02-29 8:48 ` Jonas Bonn
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=1330505774.2964.31.camel@crucifix \
--to=jonas@southpole.se \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@openrisc.net \
--cc=richard@nod.at \
/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