> On Nov 2, 2017, at 09:53, Adrian Chadd wrote:
>
> ugh okay
>
> So it's a chicken/egg problem.
>
> You can't finish the device probe/attach until the firmware loads.
>
> For iwn, you can read the chipset abilities and mac address from
> EPROM/flash on the chip without the firmware being
ugh okay
So it's a chicken/egg problem.
You can't finish the device probe/attach until the firmware loads.
For iwn, you can read the chipset abilities and mac address from
EPROM/flash on the chip without the firmware being loaded, so you can
complete probe/attach before the root filesystem i
> On Oct 29, 2017, at 11:01, Warner Losh wrote:
...
> The blobs run on the actual card itself, not on the host. This is the
> firmware for the wireless SoC that's on the card. We have allowed those in
> the kernel since the very early days of the project when scsi controllers
> like isp(4) d
On Sun, Oct 29, 2017 at 11:29 AM, Ngie Cooper (yaneurabeya) <
yaneurab...@gmail.com> wrote:
>
> > On Oct 29, 2017, at 10:26, Kevin Oberman wrote:
>
> …
>
> > But I thought that all modern wireless interfaces and many others load
> blobs. Is the source for the firmware blob for iwn (which is in GE
> On Oct 29, 2017, at 10:26, Kevin Oberman wrote:
…
> But I thought that all modern wireless interfaces and many others load blobs.
> Is the source for the firmware blob for iwn (which is in GENERIC) available?
There’s a piece that’s open sourced that a BSD developer has written,
bu
On Sun, Oct 29, 2017 at 9:49 AM, Ngie Cooper (yaneurabeya) <
yaneurab...@gmail.com> wrote:
>
> > On Oct 29, 2017, at 02:46, Thomas Mueller wrote:
>
> …
>
> > Is that binary blob the reason why rsu is not in GENERIC?
> >
> > I use rsu for Hiro H50191 USB wireless adapter.
>
> Yup.
>
But I thought
> On Oct 29, 2017, at 02:46, Thomas Mueller wrote:
…
> Is that binary blob the reason why rsu is not in GENERIC?
>
> I use rsu for Hiro H50191 USB wireless adapter.
Yup.
signature.asc
Description: Message signed with OpenPGP using GPGMail
from Ngie Cooper:
> > On Oct 28, 2017, at 18:09, Gordon Tetlow wrote:
> > I have an Intel NUC that uses an Intel 8260 wireless driver. This works
> > flawlessly if I load the module if_iwm via the loader or the rc.conf
> > kld_list directive.
> > Do we know if the iwm driver not being in GENERI
> On Oct 28, 2017, at 18:09, Gordon Tetlow wrote:
>
> I have an Intel NUC that uses an Intel 8260 wireless driver. This works
> flawlessly if I load the module if_iwm via the loader or the rc.conf
> kld_list directive.
>
> Do we know if the iwm driver not being in GENERIC is an oversight or on
I have an Intel NUC that uses an Intel 8260 wireless driver. This works
flawlessly if I load the module if_iwm via the loader or the rc.conf
kld_list directive.
Do we know if the iwm driver not being in GENERIC is an oversight or on
purpose? I couldn't find anything in the list history.
Gordon
__
10 matches
Mail list logo