From: Martijn Braam <martijn@brixit.nl>
To: Pavel Machek <pavel@ucw.cz>,
fiona.klute@gmx.de, phone-devel@vger.kernel.org,
icenowy@aosc.xyz, 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 21:33:40 +0100 [thread overview]
Message-ID: <2c720f2e-3c73-4a77-92e0-5da8fce86b3f@brixit.nl> (raw)
In-Reply-To: <ZaY44AHISMIh8fHM@duo.ucw.cz>
Hello Pavel,
Isn't this simply the case of picking the gc2145 bits from Megis tree?
https://megous.com/git/linux/tree/arch/arm64/boot/dts/allwinner/sun50i-a64-pinephone.dtsi?h=orange-pi-5.10#n410
[For the pinephone kernel development there's the option of building the
kernel using envkernel.sh in postmarketOS with
https://wiki.postmarketos.org/wiki/Compiling_kernels_with_envkernel.sh
which has some automation for building a kernel and pushing it to a
connected device. Ethernet and keyboard are replaced by ssh and
usb-networking in this case]
Greetings,
Martijn
On 1/16/24 09:05, Pavel Machek wrote:
> Hi!
>
> In 6.8-rc0, driver for gc2145 (front camera on pinephone) was merged,
> but we don't have corresponding dts entries. Does anyone have setup
> where they can fix it easily?
>
> [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.]
>
> Best regards,
> Pavel
next prev parent reply other threads:[~2024-01-16 20:33 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 [this message]
2024-01-24 19:05 ` Pavel Machek
2024-01-16 21:14 ` Fiona Klute
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=2c720f2e-3c73-4a77-92e0-5da8fce86b3f@brixit.nl \
--to=martijn@brixit.nl \
--cc=alain.volmat@foss.st.com \
--cc=fiona.klute@gmx.de \
--cc=icenowy@aosc.xyz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--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®