From: Fiona Klute <fiona.klute@gmx.de>
To: Pavel Machek <pavel@ucw.cz>,
phone-devel@vger.kernel.org, icenowy@aosc.xyz, martijn@brixit.nl,
megous@megous.com, kernel list <linux-kernel@vger.kernel.org>
Cc: alain.volmat@foss.st.com, sakari.ailus@linux.intel.com,
linux-media@vger.kernel.org
Subject: Re: Front camera on pinephone
Date: Tue, 16 Jan 2024 22:14:53 +0100 [thread overview]
Message-ID: <3f60d01d-b047-4e5d-a8d8-1debe3466629@gmx.de> (raw)
In-Reply-To: <ZaY44AHISMIh8fHM@duo.ucw.cz>
Am 16.01.24 um 09:05 schrieb Pavel Machek:
> [If you have hints how to set-up pinephone for kernel development,
> that would be welcome. Currently I have mobian with rather old 6.1
> kernel on it, and lack of keyboard/ethernet makes things tricky.]
So far I'm mostly using "pmbootstrap build --src" [1], which essentially
builds the pmOS kernel package but replaces the source with the tree I
point at. I keep thinking I should try envkernel.sh [2], which is
supposed to set up cross-compiling with the usual make flow. Maybe
that'd work with bindeb-pkg?
I don't know how well an unpatched mainline kernel would run, I'm
currently using megi's 6.7 tree [3] plus the pmOS patches as the basis
for my rtw88_8723cs development [4] (if you look at the history, it's
v6.7 -> orangepi-6.7 -> pmos-6.7 -> rtw88_8723cs). I know megi's kernel
has some DTS patches but haven't looked too deeply into the changes,
maybe some could be upstreamed together with the camera part.
Regards,
Fiona
[1] https://wiki.postmarketos.org/wiki/Pmbootstrap#Building_packages
[2] https://wiki.postmarketos.org/wiki/Compiling_kernels_with_envkernel.sh
[3] https://xff.cz/git/linux/log/?h=orange-pi-6.7
[4] https://github.com/airtower-luna/linux/commits/rtw88_8723cs/
prev parent reply other threads:[~2024-01-16 21:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 8:05 Pavel Machek
2024-01-16 20:33 ` Martijn Braam
2024-01-24 19:05 ` Pavel Machek
2024-01-16 21:14 ` Fiona Klute [this message]
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=3f60d01d-b047-4e5d-a8d8-1debe3466629@gmx.de \
--to=fiona.klute@gmx.de \
--cc=alain.volmat@foss.st.com \
--cc=icenowy@aosc.xyz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=martijn@brixit.nl \
--cc=megous@megous.com \
--cc=pavel@ucw.cz \
--cc=phone-devel@vger.kernel.org \
--cc=sakari.ailus@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®