By accident, one of the el-cheapo motherboards I used about 6 years ago ran with MAC 00:00:00:00:00:00. Interestingly, this wasn’t a problem — I could still communicate with my router and didn’t even notice this for a long time. But then I tried to communicate with my father’s IRIX machine, and we couldn’t get it to work. Until we realized the misconfiguration :).
Perhaps a lot of brute-force try-them-all routines skip the all zeros option, and others consider an all zeros result to be invalid (internally mapped to a "no match" result or so forth). A truer security through obscurity idea I can't imagine though so if that is the case "arguably more secure" is very arguable!
Great to see the entry cost of an embedded linux development kit dropping from over $500 few years ago, down to the price of a pizza or two.
This means we're going to see more young talented developers with actual embedded system skills.
Will the Pi really teach you embedded system skills?
I don't want to be a cynic, but I don't see how this board makes it easier to control anything or interface to any other device. It's still Linux and it's typical set of drivers, right? How will the Pi or the upcoming add-on interface board let me connect an LVDS LCD or capacitive touchscreen? You mean I still have to hack up an I2C device driver and wire it up? I need to spin a kernel? Is there an open-source video driver for the Broadcom chip?
I think it's a nice idea to put a cheap laptop into the hands of students. But I'll be more curious to see what those first 10 boards will be used for other than tiny MP3/MP4 players. You're still in Linux-land and that's not the most friendly environment for embedded systems programmers.
Resourceful and talented developers can do a hell of a lot with a cheap Arduino or garage-sale laptop, they don't need a magical new Broadcom EVK to do this.
well, one can learn a lot of things if he or she is motivated enough:
* Building a bootloader from sources. Trying various boot media sources and ways to launch your code in the raw memory. Probably even some assembler stuff.
* Learning how an embedded system is built, from kernel patches to busybox
* Learning how a community embedded Linux project works, with Git workflow, tests and updates
* The board is small enough to place on a moving platform and learn how the real-time linux interacts with physical environment
17 comments
[ 3.1 ms ] story [ 48.2 ms ] thread:)
And a price with lots of zeros in it, it would seem! (All in a good cause of course.)
Currently more than 10x the normal price.
I don't want to be a cynic, but I don't see how this board makes it easier to control anything or interface to any other device. It's still Linux and it's typical set of drivers, right? How will the Pi or the upcoming add-on interface board let me connect an LVDS LCD or capacitive touchscreen? You mean I still have to hack up an I2C device driver and wire it up? I need to spin a kernel? Is there an open-source video driver for the Broadcom chip?
I think it's a nice idea to put a cheap laptop into the hands of students. But I'll be more curious to see what those first 10 boards will be used for other than tiny MP3/MP4 players. You're still in Linux-land and that's not the most friendly environment for embedded systems programmers.
Resourceful and talented developers can do a hell of a lot with a cheap Arduino or garage-sale laptop, they don't need a magical new Broadcom EVK to do this.
* Building a bootloader from sources. Trying various boot media sources and ways to launch your code in the raw memory. Probably even some assembler stuff.
* Learning how an embedded system is built, from kernel patches to busybox
* Learning how a community embedded Linux project works, with Git workflow, tests and updates
* The board is small enough to place on a moving platform and learn how the real-time linux interacts with physical environment