linux-kernel - Re: [PATCH 1/1] [Blackfin try #2] char driver for Blackfin on-chip OTP memory

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]

Message-ID: <20080326190917.GB24954@uranus.ravnborg.org>
Date:	Wed, 26 Mar 2008 20:09:17 +0100
From:	Sam Ravnborg <sam@...nborg.org>
To:	Mike Frysinger <vapier.adi@...il.com>
Cc:	Jiri Slaby <jirislaby@...il.com>, Bryan Wu <cooloney@...nel.org>,
	linux-kernel@...r.kernel.org, Wim Van Sebroeck <wim@...ana.be>
Subject: Re: [PATCH 1/1] [Blackfin try #2] char driver for Blackfin on-chip OTP memory

> 
> >  > also, it isnt "broken" in the sense that it "doesnt work" ;)
> >
> >  Gcc simply doesn't allow that, you likely got 2 sections with init.data, with
> >  and without readonly bit set, which is wrong, and it seems, that on some systems
> >  (debian) you won't even compile it.
> 
> gcc-4.1.2/binutils-2.17 doesnt have a problem compiling/linking the
> code in question.  and i imagine i would have noticed a build/link
> failure long before testing it on actual hardware.
target arch dependent. Try with 64 bit powerpc.

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