51–60 of 218 posts
Why does Raspberry Pi not need to conform to the new "standards" of the FCC that require locking down firmware in routers? If it has onboard wifi, and you can turn it into a router... what's the difference between someone installing OpenWRT on a raspi vs. installing OpenWRT on a TPLink? edit: This is a legitimate question, not an opinion.
The onboard Wifi and Bluetooth really makes the barrier of entry for IoT $5 (assuming the stick with the $5 mark)
Full WiFi stack, 11x GPIO, Analog in, SPI, I2C, 80/160Mhz, 4MB Flash, power/flashing over USB, supported by the Arduino IDE, or just use the NodeMCU Lua firmware with modules for most sensors, displays, MQTT etc. I'm having a blast with them right now.
Why does Raspberry Pi not need to conform to the new "standards" of the FCC that require locking down firmware in routers? If it has onboard wifi, and you can turn it into a router... what's the difference between someone installing OpenWRT on a raspi vs. installing OpenWRT on a TPLink? edit: This is a legitimate question, not an opinion.
Why does Raspberry Pi not need to conform to the new "standards" of the FCC that require locking down firmware in routers? If it has onboard wifi, and you can turn it into a router... what's the difference between someone installing OpenWRT on a raspi vs. installing OpenWRT on a TPLink? edit: This is a legitimate question, not an opinion.
Do you have any more info on this new "standard" from the FCC? If true, that…sucks.
It was widely (and incorrectly) reported as requiring all routers to have locked firmware, but that's not really the case, and if the proposal were to go forward there are a variety of ways that the SDR could be locked down while allowing firmware updates in general.
It's not clear that the FCC is even going to go forward with it, though; industry pushback was quite heavy.
edit: it looks like they went forward with the guidance, after amending it to be clear they specifically weren't going after open-source firmware
Earlier quoted context omitted.
If I may add - do yourself the pleasure, and use a standard usb Xbox 360 controller, otherwise you are in for a world of pain. I've tried a NES30 controller over bluetooth and after a week of trying different configurations nearly chucked the whole thing in a bin. Also some of the emulators are too slow to be usable, even on the Rpi 2, NES and SNES work absolutely fine, but MAME, N64 and Dreamcast are more like curio…
Actually, for N64 emulation, I have a 100% full speed fork of Mupen64Plus for the Pi 2 sitting around on my hard disk that I hacked together a while ago. I should really clean it up and post it to GitHub. There's no fundamental reason why the N64 can't be emulated at full speed on that hardware. The VideoCore IV blows the RDP away in fill rate, after all. It's just that the available video plugins are old and aren't…
I'm a little disappointed that (from a brief glance at the documents) it doesn't appear to support the 5 Ghz Wi-Fi band. I wonder if it's a power issue, or just limited space on the PCB. The 2.4 Ghz band gets kind of crowded in dense urban environments.
I couldn't spot the typical wavy PCB antenna pattern anywhere. Is that small cube in the upper left corner of external top view a ceramic antenna? Looks to me like the 2 LEDs have been shifted further down towards lower left and replaced with something new. Update: Just noticed the radio testing report says single PCB mounted chip ceramic. I still can't spot it with certainty.
I cant believe it took them that long, Broadcom is famous for their BT/Wifi chips, buildin wifi was a no brainer, and cost shouldnt be an issue when you have great connections inside the company.