The forum was deliberately blocked from 10:30GMT until 23:30GMT.jdb wrote: Belated because our website was on fire for pretty much all of the launch day.
Our website was on fire *despite* load-shedding the forums. Your point?DougieLawson wrote:The forum was deliberately blocked from 10:30GMT until 23:30GMT.jdb wrote: Belated because our website was on fire for pretty much all of the launch day.
<OFF-TOPIC type="annoyance">jdb wrote:Our website was on fire *despite* load-shedding the forums. Your point?DougieLawson wrote:The forum was deliberately blocked from 10:30GMT until 23:30GMT.jdb wrote: Belated because our website was on fire for pretty much all of the launch day.
So for a 13 hour period where the primary purpose of this site was to inform, rather than to discuss, we should have spent at least order of magnitude more on bandwidth, computational resource and logistics to ensure that the discussion platform was available for those precious 13 hours?DougieLawson wrote: The point being that the Foundation knew they were going to launch today, they could have rented extra capacity from Mythic to support the expected extreme workload (based on extrapolating figures from July (B+) and November (A+)). Removing a significant support resource isn't good for the community.
uSD generally wasn't CPU limited on 2835.Lob0426 wrote:Has the Foundation ran any performance tests on the Micro SD and the USB that show improvement?
Though I have not seen any corruption issues with the newest software updates (in more than a year), do you expect any of these issues to reoccur in the new board?
I have seen mention that the USB on chip was not modified. I have not heard much mention about the SD transfers as yet.
Currently the ARMv6 userland (Raspbian et al) is default.TimG wrote:I'm curious about ARMv6 vs ARMv7. I understand from the announcement that the new CPU can run Raspbian ARMv6 code, but presumably standard Debian ARMv7 code will be faster. Can we switch between Raspbian and Debian repositories without running into problems?
The Cortex-A7 architecture has built-in support for Hypervisor modes and some tricks that make virtualisation "easier".mckenzba wrote:Since the new BCM2836 is a Cortex-A7 chip and we know it supports neon (and presumably vfpv4-d32/udiv/sdiv), does this chip also support hardware virtualization? (It would be really cool to run xen on this thing!)
To use an existing card on Pi2 you needgdw35 wrote:I currently have a Model B that I have set up for media and gaming, as well as a bit of development (also have LCD display attached). I was hoping I could just swap this out for the Pi 2. Am I able to just copy the SD card I am using for the Model B to a micro -SD for use on the Pi 2, or do I need to start from scratch again and set it all up again?
If I can just copy the SD card is there anything I need to do or change after booting the first time (i.e. config changes, setup, etc.)?
Thanks for reply.jdb wrote:To use an existing card on Pi2 you need
- Recent firmware
- ARMv7 kernel modules.
To upgrade an SD card for Pi 2 use:
sudo apt-get update && sudo apt-get upgrade
Since you know that Android on the Pi2 will be unofficial if it happens, how can that be answered by any person right now? If you build it, they will come.ric96 wrote:will their be support for android (unofficially, i know their wont be any from the foundation itself) now that the hardware is more than capable?
Everything I've seen about Win10 IoT suggests that it is all CLI. Maybe the Pi2 can run (limited?) GUI apps that have been deployed to it though? I haven't found any certain information.Efcis wrote:According to other posts, Win10 for Pi2 won't have any GUI. Can you confirm ?
And what about the Ubuntu distro for the Pi2 ?