On 18/04/2014 13:46, Christoph Egger wrote:
>> > That's very straightforward. See the pathnames in firmware_map[] table (iwn
>> > in this case).
> Is this map local? If it is going to be used in "normal" FreeBSD we
> probably need to agree (in some way) on the content. if it's debian only
> we coul
Robert Millan writes:
> On 15/04/2014 11:31, Christoph Egger wrote:
>> It's ~600kB. I've increased the limit locally to 1 MiB which gets me
>> working wifi using the linux firmware package
>
> Nice. Well, feel free to commit that change in kfreebsd-{10,11} if you
On 15/04/2014 11:31, Christoph Egger wrote:
> It's ~600kB. I've increased the limit locally to 1 MiB which gets me
> working wifi using the linux firmware package
Nice. Well, feel free to commit that change in kfreebsd-{10,11} if you
can confirm it works.
> and some symlinks
Robert Millan writes:
> On 10/03/2014 10:10, Christoph Egger wrote:
>> It seems kfreebsd-11 does not want to load the iwlwifi firmware from
>> the "linux" package (talks about firmware being to large). Will this
>> work in the future or do wen need separate fi
On 10/03/2014 10:10, Christoph Egger wrote:
> Hi!
>
> It seems kfreebsd-11 does not want to load the iwlwifi firmware from
> the "linux" package (talks about firmware being to large). Will this
> work in the future or do wen need separate firmware packages anyway?
The
Hi!
It seems kfreebsd-11 does not want to load the iwlwifi firmware from
the "linux" package (talks about firmware being to large). Will this
work in the future or do wen need separate firmware packages anyway?
Christoph
--
9FED 5C6C E206 B70A 5857 70CA 9655 22B9 D49A E
Your message dated Sat, 08 Feb 2014 15:51:45 +
with message-id
and subject line Bug#642468: fixed in kfreebsd-10 10.0-2
has caused the Debian Bug report #642468,
regarding kfreebsd-8|9 does not provide any method to use non-free firmware
blobs
to be marked as done.
This means that you claim
Robert Millan writes:
> On Mon, Oct 15, 2012 at 03:48:41PM -0700, Christoph Egger wrote:
>> Currently the only way freebsd really supports firmware loading is
>> through kernel modules.
>
> FYI, latest kfreebsd-11 supports loading blobs from /lib/firmware.
Just seen the co
Hi,
On Mon, Oct 15, 2012 at 03:48:41PM -0700, Christoph Egger wrote:
> Currently the only way freebsd really supports firmware loading is
> through kernel modules.
FYI, latest kfreebsd-11 supports loading blobs from /lib/firmware.
--
Robert Millan
--
To UNSUBSCRIBE, email to debian-bs
Your message dated Wed, 08 Jan 2014 10:05:57 +
with message-id
and subject line Bug#642468: fixed in kfreebsd-11 11.0~svn260207-2
has caused the Debian Bug report #642468,
regarding kfreebsd-8|9 does not provide any method to use non-free firmware
blobs
to be marked as done.
This means that
2013/7/31 Christoph Egger :
> Hi!
>
> I'm trying to build a firmware-enriched kfreebsd-9.1 kernel. However
> some of the drivers disabled FTBFS (see below). What would be the
> convenient way to disable the failing drivers
You can edit them out in sys/modules/Makefile
Al
Hi!
I'm trying to build a firmware-enriched kfreebsd-9.1 kernel. However
some of the drivers disabled FTBFS (see below). What would be the
convenient way to disable the failing drivers (or get the iwn*fw.ko)?
Christoph
===> nve (all)
uudecode <
/home/christoph/scratch/kfreebsd-9
Package: wnpp
Severity: wishlist
Owner: Christoph Egger
* Package name: kfreebsd-9-firmware-nonfree
Version : 9.0
Upstream Author : FreeBSD
* URL : http://www.freebsd.org/
* License : multiple, nonfree
Programming Lang: blobs, C
Description : Nonfree
Debian Free Software Guidelines" [3]. In that spirit there should at least be
> the
> /possibility/ to use non-free bits on Debian systems.
Nobody's arguing against it, but still someone has to do the work.
> The FreeBSD kernel supports [4] loadable firmware, but support for this
nel with bce
>
> whats bce?
My firmware NIC driver (bnx on Linux), I took as example.
Besides: Same here, many thanks Petr, for providing a howto how to build
a kernel including non-free sources, although that's probably not a
solution for end users :)
Since that seems more straightforward
ABI
- not distributable and may be distributable firmware
- distributable, but non-free
The first set is disabled via 903_disable_non-free_drivers.diff
and 2nd and 3rd via 999_firmware.diff.
Our manpower is simply limited ...
Petr
--
To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23.09.2011 15:32, Holger Levsen wrote:
> Hi Petr,
> On Freitag, 23. September 2011, Petr Salinger wrote:
>> Here is the recipe for building own kernel with bce
>
> whats bce?
My firmware NIC driver (bnx on Linux), I took as
Hi Petr,
thanks for your howto!
On Freitag, 23. September 2011, Petr Salinger wrote:
> Here is the recipe for building own kernel with bce
whats bce?
cheers,
Holger
--
To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact lis
This firmware is being removed from the kfreebsd kernel leaving no (easy)
possibility
to use kfreebsd on such a server as there is no possibility to load non-free
firmware
at runtime, like we do on Linux. Its neither (easily) possible to rebuild the
kernel
from scratch including firmware, as
ir servers. Unfortunately pretty much every modern server comes with mounted
NICs which do require some sort of firmware. In my case its the bce(4) aka bnx
on Linux chipset used widely in IBM, HP and Dell servers.
This firmware is being removed from the kfreebsd kernel leaving no (easy)
possibility
to use k
20 matches
Mail list logo
