From: Chris Gorman <email@example.com>
To: 9fans <firstname.lastname@example.org>
Subject: Re: [9fans] applying a patch on 9front
Date: Wed, 1 Feb 2023 13:25:11 -0500 [thread overview]
Message-ID: <CAHVeOW9MYX8SYSR1h4BX=+YA4HcPtp5cnhLmq1oToH69Q_odiA@mail.gmail.com> (raw)
To get the patch to apply on my system, I used
cat $home/etheriwl.c.diff | ape/patch -p5
Then you need to copy iwm-7265-17 from the openbsd firmware blobs and
put it into /lib/firmware, then build your kernel.
This will configure the iwm-7265-17 firmware blob to load with an
ac-7265. Unfortunately, not all ac-7265's require this particular
blob. I have another one that requires the iwm-7265D-29. It also
identifies itself with the same pci id, 0x095a, so there is no way to
differentiate which firmware to load at the moment. You have to know
what firmware the ac-7265 needs and then code etheriwl.c to suit.
Good luck and I hope you get your wireless working. I kind of gave up
on mine as I couldn't get it to work at boot, but if you get it
working let me know.
On Wed, Feb 1, 2023 at 8:05 AM <email@example.com> wrote:
> i am trying to patch etheriwl.c on 9front. the patch is available on this list under the topic "modification of etheriwl.c for intel ac 7265". however i can not get the patch to apply. how do i do this? i have tried both 'git/import' and 'ape/patch' to no avail. any help would be appreciated. thanks for your time.
> 9fans / 9fans / see discussions + participants + delivery options Permalink
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2023-02-01 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 13:05 jimerickso
2023-02-01 18:25 ` Chris Gorman [this message]
2023-02-01 18:55 ` jimerickso
2023-02-01 19:08 ` ori
2023-02-01 19:20 ` Chris Gorman
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).