From: Tony Lindgren <tony@atomide.com>
To: "Woodruff, Richard" <r-woodruff2@ti.com>
Cc: David Russell <david.russell73@gmail.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [EXTERNAL] OMAP2430 kernel hangs on ioremap of IVA2.1 addresses
Date: Thu, 12 Aug 2021 09:32:28 +0300 [thread overview]
Message-ID: <YRTAfDeGemh7Bt50@atomide.com> (raw)
In-Reply-To: <6616af990c3d4cc8b3ca51e1a6e9283e@ti.com>
Hi,
* Woodruff, Richard <r-woodruff2@ti.com> [210811 14:18]:
> Probably a good minimal kernel with basic drivers can be made at multiple points. I'm less sure about the state of open drivers with WL18xx. I'd suggest exploring that a bit more to see if it ends up dominating. For early WLAN, sometimes firmware and fragile DMA integrations were hard to work around.
The wl17xx wl18xx driver is behaving OK with various SoCs with the mainline
kernel at least as tested with SDIO.
For the Linux kernel, often the most recent long term kernel is used, that
is linux-5.10.y currently and might be linux-5.15.y at the end of the year.
If you just need basic SoC support and wl18xx, then I don't see issues
using current stable kernels. The SoC is fairly similar for peripherals
for various omap3 devices that are still being actively used :)
If you need to use out of tree hardware accelerators and and power
management, then things might get a bit trickier.
Regards,
Tony
next prev parent reply other threads:[~2021-08-12 6:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 15:01 OMAP2430 kernel hangs on ioremap of IVA2.1 addresses David Russell
2021-06-07 15:40 ` [EXTERNAL] " Woodruff, Richard
2021-06-09 6:20 ` Tony Lindgren
2021-06-09 12:11 ` David Russell
2021-06-11 4:43 ` Tony Lindgren
2021-08-11 12:54 ` David Russell
2021-08-11 14:17 ` Woodruff, Richard
2021-08-12 6:32 ` Tony Lindgren [this message]
2021-08-12 19:05 ` Woodruff, Richard
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YRTAfDeGemh7Bt50@atomide.com \
--to=tony@atomide.com \
--cc=david.russell73@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=r-woodruff2@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.