> Could you clarify the commit log (like “Add CONFIG_HOTPLUG_PCI=y.”), and
> mention “For USB-C/Thunderbolt devices. Tested it with an USB-C to HDMI
> adapter.” in the log as well?
It's actually a duplicate definition. Missed it when searching the
file, it was probably missing from my custom buggy
David Craven skribis:
> * gnu/packages/linux-libre-4.9-x86_64.conf
> * gnu/packages/linux-libre-4.9-i686.conf
Could you clarify the commit log (like “Add CONFIG_HOTPLUG_PCI=y.”), and
mention “For USB-C/Thunderbolt devices. Tested it with an USB-C to HDMI
adapter.” in the log as well?
Thanks!
L
> If the device has internal storage and if someone wanted to
> target you and did have the resources to do so, they could reflash the
> chip and you'd never know.
They can't if it's read-only (and if they are without physical access to the
room). On the other hand, if they had physical access th
Mmh, I think that forcing binary blobs out of the linux kernel is only
useful if vendors move more work into the driver and silicon instead
of firmware that cannot be updated, since each flash device is a
security risk. But it could also backfire. The thunderbolt firmware
for example is only update
Hi Danny,
> For example, let's say Intel had non-updateable microcode on its CPUs and it
> included a backdoor. If anyone *ever* found it, nobody would trust Intel ever
> again - and Intel couldn't sweep it under the rug because millions of
> physical chips that include the backdoor would be in
Hi David,
On Thu, 2 Feb 2017 21:18:06 +0100
David Craven wrote:
> > I don't think the firmware needs to be uploaded at all to the AR9285
> > device.
>
> I don't understand:
>
> 1. free firmware - anyone can update the firmware
> 2. binary blob - the vendor can update the firmware
> 3. fixed
> I don't think the firmware needs to be uploaded at all to the AR9285 device.
I don't understand:
1. free firmware - anyone can update the firmware
2. binary blob - the vendor can update the firmware
3. fixed at manufacturing time - no one can update the firmware
Option 1 is obviously superior
Hi David,
I have an Atheros AR9285 in GuixSD and it works.
/sys/class/net/wlp2s0/device/driver says it's using the driver ath9k PCI.
On Thu, 2 Feb 2017 18:07:22 +0100
David Craven wrote:
> I'm having trouble finding information. The opened atheros firmware is
> only for the AR7010 and AR9271 U
> I was surprised that linux-libre works on the dell xps 13. I'm
> considering buying an atheros wifi card, since that's the only thing
> that does not work. Does anyone know how to find out if there is a
> BIOS whitelist/blacklist? So it's just ARM boards that don't work with
> linux-libre?
I'm h
I was surprised that linux-libre works on the dell xps 13. I'm
considering buying an atheros wifi card, since that's the only thing
that does not work. Does anyone know how to find out if there is a
BIOS whitelist/blacklist? So it's just ARM boards that don't work with
linux-libre?
This is for new USB-C/Thunderbolt devices. Tested it with an USB-C to
HDMI adapter.
11 matches
Mail list logo
