narmstrong changed the topic of #linux-amlogic to: Amlogic mainline kernel development discussion - our wiki http://linux-meson.com/ - ml linux-amlogic@lists.infradead.org - official channel moved from Freenode - publicly logged on https://libera.irclog.whitequark.org/linux-amlogic
djrscally has quit [Ping timeout: 265 seconds]
vagrantc has quit [Quit: leaving]
naoki has joined #linux-amlogic
hexdump0815 has quit [Ping timeout: 265 seconds]
hexdump0815 has joined #linux-amlogic
buzzmarshall has quit [Quit: Konversation terminated!]
djrscally has joined #linux-amlogic
asriel has joined #linux-amlogic
ldevulder has joined #linux-amlogic
llu has quit [Ping timeout: 260 seconds]
dlan has quit [Ping timeout: 276 seconds]
llu has joined #linux-amlogic
dlan has joined #linux-amlogic
GNUtoo has quit [Ping timeout: 265 seconds]
GNUtoo has joined #linux-amlogic
<f_> Hello! I'm trying to get an Amlogic board working as part of a generic arm64 port, only to notice that ttyAML0/ttyMSM0/ttyWHATEVER0 soc-specific thing
<f_> What's the current situation regarding ttyAML0? Did it get deprecated, or can ttyS0 be used instead?
<xdarklight> f_: iirc on the latest Amlogic SoCs we register ttyS while all older ones are still using ttyAML (to not break existing setups)
<f_> I'm on A311D
<f_> xdarklight: Wouldn't it be possible to register both on the older ones?
<f_> So that older setups don't break, while newer setups can make use of ttyS
<f_> in theory
<xdarklight> not sure if that would work. it probably means that Linux receives incoming data also for both "ports" - that's probably not going to end well
<f_> I more meant symlinking one of them
jacobk has joined #linux-amlogic
f_ has quit [Ping timeout: 246 seconds]
f_ has joined #linux-amlogic
naoki has quit [Quit: naoki]
<narmstrong> f_: if you find a solution, you’ll have my sympathy!!!
<narmstrong> It’s no more an issue with systemd anyway
<narmstrong> And it you specify nothing in the kernel cmd line the first serial will be used anyway
shoragan has quit [Read error: Connection reset by peer]
shoragan has joined #linux-amlogic
<f_> narmstrong: In the end I think I'll just do some udev hackery
<rockosov> f_: Hello! I've sent ttyS support for all new Amlogic some time ago. Old SoCs still have ttyAML mask
<f_> rockosov: yeah, I also saw the driver, but I'm on g12b
buzzmarshall has joined #linux-amlogic
<rockosov> But we have faced with a problem to support both tty prefixes on the uboot side. We need a way to boot kernel with ttyS (vendor kernels) and ttyAML (upstream kernels). CMDLINE_EXTEND is not working for arm64 arch, and I've prepared the patch to uboot to support fdt chosen/bootargs setup. Maybe it will help to you.
<rockosov> I describe to problem wider there
<rockosov> narmstrong: How about adding a Kconfig entry to set up the tty prefix name for legacy SoCs? If you're aware that your setup already uses the old 'ttyAML' name, you can leave the configuration as is. Otherwise, you should configure it to use the 'ttyS' name. Another option... as I know tty subsystem doesn't have any 'aliasing' functionality
f_ has quit [Ping timeout: 248 seconds]
f_ has joined #linux-amlogic
psydroid has quit [Read error: Connection reset by peer]
psydroid has joined #linux-amlogic
Terry13732293409 has quit [Quit: Bye Bye]
Terry13732293409 has joined #linux-amlogic
<exkc> f_
<f_> exkc
<exkc> hi
ldevulder has quit [Quit: Leaving]
montjoie has quit [Ping timeout: 248 seconds]
montjoie has joined #linux-amlogic
naoki has joined #linux-amlogic
naoki has quit [Client Quit]
naoki has joined #linux-amlogic
jacobk has quit [Ping timeout: 248 seconds]
djrscally has quit [Ping timeout: 244 seconds]