I was paid $50 to get my phone (free with rebate).. now the service, that's another story. But they go hand-in-hand, so you can't really separate them. It's an HTC Sensation, and is my first foray into smartphones. It's cool - but I really still don't get how people can't live without them. And I'm no luddite, hell I used to work for THE cell phone company back in the day and had one of the first flipphones and first StarTacs. I got those because it was cool.. now I just find them annoying for the most

They can be separated and are in many countries. You were not paid $50 from your phone company. You received a loan from your phone company for the cost of the phone plus the fifty dollars. You will repay the loan over the next few years in the form of inflated rates for your service. If you continue to use the phone on their network beyond your contract terms then you will still be paying the subsidy without getting any benefit.

The bigger performance problem so far are the X window system device drivers.Right now it seems the driver is just a frame-buffer driver and the CPU does all the work,and is not using the GPU.Until they write accelerated drivers, the performance will by slow.

This is indeed what I said on Engadget; this announcement basically says the team compiled most of the stuff for hardware-FPU whereas previously it was either using software-FPU or had both codes compiled-in, as such this stuff does indeed help CPU-bound software that is heavy on the maths, but doesn't really do anything for basic bit-blitting or linear gradients used in graphics. Most of the "slowness" - complaints I see when reading any RPi-related news is exactly due to CPU having to do all the drawing.

It's been a long time now since I been lurking around the RPi forums, but so far I have not heard of plans to bring out an accelerated X-driver which is quite a shame. It really limits the usefulness of the system. I still hope the devs do come around to it eventually, though.

Because its optimized for the Raspberry Pi hardware and the tweaks it uses are likely to be near worthless for most other hardware. Its like all the distributions that were coming out for the EEE PC (first low cost netbook to gain popularity) which had the main advantage of being really easy to install/use on the particular platform. In other words, instead of spending a few hours configuring Debian to optimize it for my hardware I can just install a simple OS.

quit your trolling.the pi foundation already has two debian releases that do use Debian mainline. the reason the raspian guys are re-building everything is because Debian doesn't do a port that supports hf on arm6. if you hate it so much, try convincing Debian to add a new port...the raspian guys already automatically merge mainline updates.

For the great majority of Raspbian users, for practical purposes the answer is "No". Packages from the Debian repositories cannot and should not be used with Raspbian. However, if you really know what you are doing and can deal with a file system that may no longer boot, it may be possible to get certain select Debian packages working with Raspbian. The rest of this answer deals with how that might be done.

Debian armel packages use the soft float ABI which is incompatible with the hard float ABI used by Raspbian. In theory it should be possible to install Debian armel packages in parallel with Raspbian packages using multiarch. However multiarch setups conflict with a hack we had to make to support the videocore libraries and there are other potential issues too. As such we don't currently recommend or support multiarch configurations with Debian armel and Raspbian armhf.

Debian armhf packages should be compatible with raspbian packages but a system with such a mixture WILL NOT RUN ON THE PI. Furthermore there may be corner cases where libraries build slightly differently on Raspbian. Such mixed systems can be useful for development (they were used heavily in the process of creating Raspbian) but are not recommended for general use.

Architecture independent ("arch all") packages are compatible between Debian and Raspbian. Source packages should in general be compatible though some may need modification to adjust compiler settings (most Debian packages just use the compiler defaults but some use their own settings for various reasons).

Short answer: because that is what debian does and if you want to remain sane when rebuilding something as large as Debian you try and stay as close to what they do as possible.

Long answer: while there is some limited support for cross-compiling in the debian tools it is very poorly documented and there is absoloutely no requirement for individual packages to support being cross compiled, let alone any testing as to whether packages meet that requirement. Trying to cross-build would mean that in addition to

A number of years ago I was developing for some Linux based PDAs (Sharp Zaurus), and the main issue I had with cross compiling was that a package's "configure" script would inspect the machine it was running on, so wouldn't produce proper configs for the target platform, among other similar issues. So what I did then was run the builds on the target platform, but use distcc so that it would shove over the pre-processed C files over to my main host to cross compile. The resultant binaries were identical to

Mainline Debian ships with binary kernels for various ARM platforms. Once you recompile the kernel and change enough of the surrounding software infrastructure to support a very specific platform, it pretty much has to become a fork. There are a number of examples of this with Debian.

The debian foundation has two ARM binary versions, the 'performance' version (armhf) that's compiled for ARMv7 or better chips, and the 'compatible' (armel) version that's compiled for IIRC ARMv4 or better.

One of the reasons the pi is so cheap is it uses an older SoC, based on ARMv6. The cortex chipsets A9 you see in say, the iphone or samsung SoC are ARMv7 instruction set based. So up to now, the standard raspberry pi debian distro was the vanilla armel squeeze, with a wheezy armel beta. However, the pi ARMv6 does have floating point hardware that allows for 'hardfloat' compilation rather than the 'softfloat' compilation option - which is used in the ARMv7 version of debian, but not the armel version. Using the hardware support for floating point calculation is obviously faster than doing it in software emulation, thus the new port to take advantage of every little bit of performance you can get out of the $5 SoC on the pi.

So raspbian is basically debian ARM, but all the binary packages have been recompiled with the hardfloat option to take advantage of the floating point hardware; they're using wheezy as the target, which is current debian testing IIRC. It's debian armhf, but compatible with the v6 pi. The Debian Foundation weren't interested in supporting a 3rd version of debian on ARM hardware, which is entirely fair enough - the amount of people interested in an ARMv6 with hardfloat who aren't using the pi is going to be very small, though they can of course run raspbian on their hardware too if they also have ARMv6 with hardware floating point; it's not like debian are rolling in money themselves. They were happy for a 'roll your own' version though, which is what has happened.

Last I checked, the raspbian project team (which is basically two guys) had successfully compiled basically everything in the debian package tree, along with keeping up to date with the constantly changing nature of debian testing; they had a compile farm running continuously to keep up, and the setup is worth reading about when the raspbian site comes back; it's a tiny operation that's giving hundreds of thousands of pi owners a significantly faster default distro on a shoestring budget. I think it's brilliant, and is an excellent example of why open source is so awesome. Want an entire OS and software custom compiled to get every ounce of performance out of the hardware? Go for it! And look, these guys have done it for you!

Good question, the changes we make in raspbian come into basically three categories.

1: changing compiler defaults. Theese can't be pushed upstream until/unless the debian tools get an understanding of flavours*. This is a subject I intend to bring up on the debian mailing lists in-time but it may well cause a flamewar.2: hacks, it's inevitable that when you have only two people doing a project on this scale that you will run into issues that you don't have the manpower to solve properly and so have to hack around to keep things moving forward. Such hacks include things like reducing optimisation levels, using non-default gcc versions and disabling testsuites. I don't think debian would want these changes.3: proper bugfixes, I do try and push these back to debian where possible.

We do not intend to be a fork, the VAST majority of source packages are imported from debian and rebuilt with no source changes whatsoever.

* a flavour is a variant that is binary compatible but has different minimum CPU requirements.

For only a few more dollars you could have a slightly more powerful CPU like tha allwiner A10 [wordpress.com] and a little more RAM soy you can run real debian and real ubuntu like the Beagleboard, Beaglebone and the Odroid-X can and you wouldn't need a forked, stripped linux distro, you could run the real thing. You don't need a weird graphic processor without drivers that nobody will touch, you need RAM and compatibility.

I hope they fix this in the next revision, the allwiner is selling for penauts nowadays.

Maybe an iomega iconnect no display but you can boot from a usb stick quite simply and run debian.It is much better than the original firmware. I was surprised to find it installed gimp when i was installing sane (for a hp multifunction which was only supported for printing by iomega's firmware) so i tried it gimp2.8 on a nas:) minidlna is much more reliable than the twonky media server that comes on the std firmware. there is 256mb of ram costs about euro 50 and uses about 5 watts. there is a kernel with

Exactly my thought. I'm thinking of it as a replacement for the Linksys NSLU2 slugs I've been using as media servers for the past 6 years or so. And since X11 is available for the platform then we'll have interactive terminals, editors, and graphical clients running on the Raspberry Pi that don't need a local graphics display (which is the case for the Linksys NSLU2).

I'd welcome an A15 based board that would allow me to replace my current desktop, an aging, although perfectly sufficient AMD Sempron 64, with something comparable in speed yet much less power hungry, something that could be almost always-on. It's probably a slightly different task but it eludes me why there doesn't seem to be any development in this area - something Efika-MX-style, only with a more modern ARM core.

A few more dollars, so like, $40? Okay, I'd do $40 for a more powerful CPU and more RAM. Maybe $50? Sure, I have the cash. I mean, it goes against the goal and purpose of the Raspberry Pi, so it might not make the target audience happy, but sure.

Except, just some minor googling seems to put the items you're listening at $90 to $150. That's not a few more dollars. That's two to four times the cost.

Somewhere in between $50 and $90 is $72.49, which is the price for the Oval Elephant: http://www.ovalelephant.com/p-2062-mini-pc-android-linux-linaro-a10-chip-1gb-ddr3-ram [ovalelephant.com]I've bought one of them, and it was shipped today. It's got a fair bit more oomph (1,5GHz Allwinner A10) than the RPI, a much neater package, an much more ram. Oh, and it's got 4GB internal flash, so you're not dependant on a SD card. It also has BGN wifi built in. It should shortly be able to run XBMC on android 4, although without HW decoding yet. It can also run linux.

Of course, it's slightly more than twice as expensive as the RPI. But it's way more than twice as valuable IMO.

Anyone please do not propose devices without GPIO/I2C/SPI/UART pins as a replacement for Raspberry PI. For many people this is key feature of RPI. 99% of those "replacement" were available long before raspberry (Gumstick/PogoPlug/etc). Problem was when you were looking something that can interact with physical world, such eval boards with similar performance were and are avialable but with prices well above > 150-200 USD. I would be really happy if someone can show me replacement that will have GPIO/I

PSOC3 FirstTouch Starter kit costs $50 and even comes with a USB cable for programming and/or power, and a 9V battery for when you want it away from wires.

It has an Intel 8051 (remember those?), is slightly smaller than a RaspberryPi, has GPIO/I2C/SPI/UART, has an onboard FPGA to handle all of the IO as well as extra blocks for things like DSP, coms interrupts and buffers, fast hardware lookup tables, custom logic etc. Internal ADCs, internal DACs, internal comparators, internal 25mA opamps. Analogue can be

There's no way a Cortex-A8 1Ghz is ~4 times faster than a 700Mhz arm11. A factor of 2 would be a better estimate (only looking at the cpu, it also has twice the memory, not sure about the gpu if it can be used it will obviously be better than a framebuffer driver...).

depending on shipping costs, that's not/that/ much of a markup.
I ordered from element 14, and I paid $45 after tax/shipping.
AND it's backordered 4-5 weeks.
To some people (not me), having it a month earlier is worth the $25 difference

depending on shipping costs, that's not/that/ much of a markup.
I ordered from element 14, and I paid $45 after tax/shipping.
AND it's backordered 4-5 weeks.
To some people (not me), having it a month earlier is worth the $25 difference

I didn't even think of ebay, I would have done it. I paid 45 to element15 two weeks ago and now I wait..

Debian armhf in testing and unstable has a minimum CPU requirements of ARMv7-A+VFPv3-D16+Thumb2. Unfortunately, the Raspberry Pi CPU doesn't meet these specs.

What Raspbian did was rebuild virtually all Debian Wheezy packages to the ARMv6+VFPv2 specs of the Raspberry Pi. Fortunately, the armhf ABI is fully supported on ARMv6 which means that Raspbian built packages run fine under Debian Wheezy armhf. This made the port much easier than it otherwise might have been as all building occurred on Debian armhf systems and the resulting binaries just needed to be verified free of ARMv7 code.

The only confusing part is that they call the architecture "armhf". This means that you don't get an error message if you try to install debian armhf packages but they just crash when you try to run them.

The same applies if you are running debian on an older x86 box and try to install a deb built on ubuntu. Or if you try and upgrade from an older debian release to a newer one that has dropped support for your CPU variant.

Precedent is that debian architecture names specify cpu family/abi not specific CPU variants. This gives more flexibility but it does mean you can install packages that are compatible with those you have installed but are not compatible with the CPU variant you have.

The port is necessary because the official Debian Wheezy armhf release is compatible only with versions of the ARM architecture later than the one used on the Raspberry Pi (ARMv7-A CPUs and higher, vs the Raspberry Pi's ARMv6 CPU).

1.11GB seems bloated. The only spare SD card I have around is 512MB. I know, I should go out and get myself some modern SD flash, which will probably be a lot faster too. My only question is why 1.11GB...? Because you've included all the ports, or...?