Can someone please silence these managers ordering the engineers to upload a zip file instead of configuring a git repo? And why the hell don’t they just include the .git folder? And why are there people reimporting tar files into git?

At the end it’s just pissing me off and it’s kinda assholish upon the engineers whose commit logs you’ve just deleted…

At least now the new Samsung Galaxy S2 (GT-I9100G) has an OMAP4 inside.
The only usable SoC on the market.
Yes! The only!

Samsung Galaxy S2 and Asus Transformer Prime, both with Android market…
I don’t pay for software, I’m FOSS user…

WTF? Money for installing packages?
My solution for such an issue is easy.

If it costs, don’t use it

And again, increasing recursive Googling…

(3) ...however, if you have a stock eglibc
and a kernel with the erratum workaround disabled/removed,
then things seem in practice to work OK.
Speculation is that perhaps the erratum is only
a problem in marginal situations (eg if the core is very hot).

Ok, wtf. “marginal situations”?
Does that mean, the hardware has the freedom to not execute the code in cases where it hates the user, like in my case? >_>

Seriously, the core hasn’t reached high temperatures yet, but still shows sign of this bug.
Ok, cancel sign: a system where already /sbin/init segfaults is not a sign, it’s more like “no discussion”

https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/739374

Anyway. I’ve now made a portage overlay for eglibc and am cross-compiling eglibc-2.15 in this very moment.
Let’s see if switching Gentoo to eglibc solves my problems…

BTW: The overlay can be found under:
https://gitorious.org/o2s-gentoo/eglibc-overlay/trees/master

Didn’t everyone already dream of that?
Ok… Not everyone, just the hardcore nerds and hackers like me, who aren’t only using bleeding edge software but more or less blood dropping flesh wound software (yes, sometimes even -9999- ebuilds in Gentoo >_< )

I guess BenBee asked me some time ago, if this would be possible…

Yes it is
./kdetect.sh
and
./autokernconf.sh

Should do the trick.
Go to the following source: http://cateee.net/autokernconf/

Not only, that the list of hazards within a tegra2 grows and grows and the errata option list within menuconfig now already is longer then the list of boards containing this SoC…
Obviously the hazards make it impossible to use any GLIBC newer then 2.12.1 …
Folks! WTF!?

Programming errors are especially then quiet annoying when you have to process a lot of data, like, let’s say, 990MB of armv7l-hardfloat Sabayon packages.
Then a system needs two hours or so to find out that it wants to fuckup because it doesn’t like the data you feed him.

At least I’ve now uploaded at least the bases system.
So far I managed to come.

Hooray!

http://ftp.o2s.ch/pub/sabayon/entropy/standard/o2s-tegra2/

Howdy
A friend of mine owns a “Samsung Galaxy S2″
CPU-info tells us there is a SMDKV310 SoC in it:

# cat /proc/cpuinfo
Processor       : ARMv7 Processor rev 1 (v7l)
processor       : 0
BogoMIPS: 1592.52

Features: swp half thumb fastmult vfp edsp neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant     : 0x2
CPU part: 0xc09
CPU revision    : 1

Hardware: SMDKV310
 Revision: 000e
 Serial  : 304d19f743777c9e

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=blob;f=arch/arm/mach-exynos/mach-smdkv310.c;h=83b91fa777c1aeb4ca5ee95ff81f244a1641e904;hb=HEAD

Looks as there would be support for it in upstream.
Let’s see if it boots as well. ( e.g. upstream support for tegra2 is just formalism, the code in master doesn’t do anything useful)

he built humanity and saw that it was fucked up and a total fail and he walked away while whistling la-paloma to never being seen again, and humanity invented stories about him and used him as an excuse for their numerous mass murders and other crimes and invented wonders around him in order to deny their own narcissistic bizarrely distorted view of reality and put it there as the only truth.

Hi folks
I was asked recently if one could optimize runtime performance of the Linux-Kernel by compiling it with an optimized compiler.
The answer: No
Even trying to use the armv7l hardfloat gcc causes the kernel build to fail.

Hi Folks

I stumbled across the following link right now:
http://androidroot.mobi/technical/tf-secure-boot-key/

In my opinion this kind of sealing up a device is an unacceptable measurement.
I suggest you check if there is such a security measurement documented and if it is boycott the respective producer.