lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Wed, 29 Feb 2012 09:56:14 +0100
From:	Jonas Bonn <jonas@...thpole.se>
To:	Richard Weinberger <richard@....at>
Cc:	arnd@...db.de, linux@...ts.openrisc.net,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] OpenRISC: IRQ: Include module.h


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@...ts.openrisc.net

/Jonas

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ