f_ has quit [Read error: Connection reset by peer]
f_ has joined #linux-amlogic
luka177 has joined #linux-amlogic
hexdump0815 has quit [Ping timeout: 260 seconds]
hexdump0815 has joined #linux-amlogic
buzzmarshall has quit [Quit: Konversation terminated!]
chewitt has joined #linux-amlogic
GNUtoo has quit [Remote host closed the connection]
djrscally has joined #linux-amlogic
ldevulder_ is now known as ldevulder
camus has quit [Read error: Connection reset by peer]
camus1 has joined #linux-amlogic
camus1 is now known as camus
camus has quit [Quit: camus]
camus has joined #linux-amlogic
psydroid has joined #linux-amlogic
luka177 has quit [Read error: Connection reset by peer]
luka177 has joined #linux-amlogic
tsegers has quit [Ping timeout: 268 seconds]
mkorpershoek has quit [Ping timeout: 268 seconds]
hays has quit [Ping timeout: 268 seconds]
mkorpershoek has joined #linux-amlogic
luka177 has quit [Ping timeout: 264 seconds]
luka177 has joined #linux-amlogic
tsegers has joined #linux-amlogic
luka177 has quit [Ping timeout: 255 seconds]
luka177 has joined #linux-amlogic
luka177 has quit [Ping timeout: 260 seconds]
luka177 has joined #linux-amlogic
luka177 has quit [Ping timeout: 264 seconds]
luka177 has joined #linux-amlogic
luka177 has quit [Ping timeout: 264 seconds]
luka177 has joined #linux-amlogic
luka177 has quit [Ping timeout: 260 seconds]
luka177 has joined #linux-amlogic
luka177 has quit [Ping timeout: 260 seconds]
luka177 has joined #linux-amlogic
luka177 has quit [Ping timeout: 264 seconds]
marc|gonzalez has joined #linux-amlogic
<phh>
hello (ping notably narmstrong), we would like to mainline our device (Freebox Player Pop, that's an S905X2/secure boot device). It is however not buyable, since it's only available as part of our operator subscription, though there are >1M people who will be able to boot that kernel. (even though we'll gladly provide some hardware samples to maintainers). Is it acceptable to put non-buyable devices' device tree in kernel?
<f_>
I don't see why it wouldn't be acceptable IMO.
<narmstrong>
phh: hi, yes, there's plenty of development boards that are internal to vendors, and they aren't buyable, so I don't see the difference here
<narmstrong>
phh: having a real product using secure boot would be great!
<f_>
amlogic reference boards come to mind.
<f_>
Those have DTs in the kernel but aren't actually buyable.
<narmstrong>
exact, I had access to those when at BL, but they were produced only for engineers and sent to companies to evaluate the soc
<narmstrong>
but buyable hw are heavily based on them, so..
<f_>
and their DTs are (ab)used by people to get their box to boot linux lol
<narmstrong>
if it make people use mainline, then it's worth it...
<f_>
Never said it wasn't :D
<f_>
mm :/
<f_>
Looks like the dwc3 driver is too big
<narmstrong>
you don't need it for gadget
<narmstrong>
only dwc2
<narmstrong>
and only the gadget one
<f_>
Don't I need the "glue" code?
<narmstrong>
hmm, yes but it's completely independent even if it's in the dwc3 dir
<f_>
yeah so the glue driver depends on dwc3 support being enabled
<f_>
talking about CONFIG_USB_DWC3_MESON_GXL depending on CONFIG_USB_DWC3
<narmstrong>
damn, yeah, it's quite bad, it shouldn't
<f_>
:P
<f_>
It's under "*** Platform Glue Driver Support ***"
<narmstrong>
there's no good place for that...
<narmstrong>
perhaps it should be moved to drivers/usb/glue
<f_>
GXL BTW.
<narmstrong>
yeah it will be the same stuff got g12a
<narmstrong>
*for
<f_>
So in theory I only need the dwc2 gadget code?
<narmstrong>
no, the glue is needed to configure the phy and the glue code to redirect signals to the dwc2
<f_>
(and the glue code)
<narmstrong>
yup
<f_>
yeah so I'll try getting it to not depend on USB_DWC3 and see what happens
<f_>
I expect lots of undefined functions TBH
luka177 has joined #linux-amlogic
luka177 has quit [Ping timeout: 264 seconds]
<marc|gonzalez>
be back later, bye :)
marc|gonzalez has quit [Quit: Leaving.]
Terry13732293409 has quit [Quit: Ping timeout (120 seconds)]