And to be clear I never suggested adding the raspberry pi firmware to
a FSDG compliant distribution.
I don't think the suggestion I made actually qualifies the raspberry
pi firmware - or any current firmware for that matter. It was made to
encourage hardware manufacturers that are willing to dip a
> David, I think you need to give up wasting your time trying to convince
> a Gnu/Linux *Libre* list that proprietary kernel blobs are a good idea.
> Most people are here because they care more about freedom than getting
> the support of every manufacturer on the market. If you want to make
> headw
Some folks are working a free firmware for Rpi2:
https://wiki.debian.org/RaspberryPi2
What you say below is not necessarily true. You can buy libre systems.
Of course, sometimes they cost more... but in a non-ideal world freedom
sometimes comes with a price. Anyway, the point of projects like thi
> About that conversation involving some GuixSD user: He gave that kind of
> recommendation so easily? I'm shocked...
The irony is that unless you know as much about hardware as Denis you
ARE USING NON-FREE FIRMWARE. As proven by you suggestion to simply use
a different distro.
About that conversation involving some GuixSD user: He gave that kind of
recommendation so easily? I'm shocked...
Unless the conversation was cut somewhere, I didn't see indication that
you wanted/want to develop free/libre replacement for the non-free
software needed for RPI 2 to work. In this ca
On 02/14/2017 01:43 PM, David Craven wrote:
> No thank you. I don't want to use binary blobs. I'll just use another
> distro until guixsd works without binary blobs.
GuixSD isn't what requires binary blobs. The hardware is. These other
distros you use come with these proprietary blobs, and GuixSD
Hi Denis,
Thank you for your extensive feedback.
> With that we can still use WiFi by ignoring the intel wifi card and
> using an USB wifi card instead.
I considered using this option but realized that I had a buggy thunderbolt
controller in my laptop, that I can only update from a windows compu
Hi David,
David Craven writes:
>> I had followed some earlier developments but had lost track recently!
>> I'm happy to see that they have released the sources of their
>> microcontroller chip design.
>
> It's more than a microcontroller chip design. The people behind sifive are
> from uc berkel
On Fri, 3 Feb 2017 15:37:32 +0100
David Craven wrote:
> This leads to two models of loading the firmware that runs on the MCU.
>
> 1. The peripheral does not contain persistent storage and the firmware
> is loaded by the linux kernel through a standard API.
When using the Linux kernel, the firmw
> I had followed some earlier developments but had lost track recently!
> I'm happy to see that they have released the sources of their
> microcontroller chip design.
It's more than a microcontroller chip design. The people behind sifive are
from uc berkeley and also developed a full gcc toolchain
10 matches
Mail list logo
