linux-kernel - Re: [microblaze-uclinux] Re: microblaze syscall list

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] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 27 Apr 2008 12:04:46 +1000
From:	John Williams <jwilliams@...e.uq.edu.au>
To:	Matthew Wilcox <matthew@....cx>
CC:	microblaze-uclinux@...e.uq.edu.au, Arnd Bergmann <arnd@...db.de>,
	Will Newton <will.newton@...il.com>,
	Linux Kernel list <linux-kernel@...r.kernel.org>,
	linux-arch@...r.kernel.org, git@...inx.com
Subject: Re: [microblaze-uclinux] Re: microblaze syscall list

Matthew Wilcox wrote:
> On Fri, Apr 25, 2008 at 07:36:35PM +1000, John Williams wrote:
>> Please remember that MicroBlaze has been around as an arch for > 4 
>> years, just not in the kernel.org tree.  These older style syscall 
>> interfaces are all part of the uClibc and glibc ports for MicroBlaze.
> 
> So is it fair to say that you now understand this was the Wrong Way To
> Do Things, and if anyone asks, you'd recommend getting an arch merged
> into kernel.org sooner rather than later?
> 

Without question!  If some abject humility will smooth the path for 
MicroBlaze, I'm happy to show it.

By way of history, as a no-MMU arch starting on the 2.4 kernel series, 
there was no home for us in kernel.org originally, however we were 
always in the uClinux "mainline" at uclinux.org from the first release I 
did back in 2002.

We jumped in at 2.6.20 basing from some vendor patches that were never 
going to fly in kernel.org.  Since then we have been improving and 
cleaning them up to where they might actually stand a chance.

I am lobbying Xilinx (the effective "silicon vendor") as hard as I can 
to support both the push to and maintenance within kernel.org.  They had 
someone at ELC in Mountain View week before last, which is a good sign I 
think.

Cheers,

John

--
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/