+dtc list because labels are purely dts syntax. On Thu, May 11, 2017 at 8:05 AM, Uwe Kleine-König <u.kleine-koenig@xxxxxxxxxxxxxx> wrote: > Hello, > > on an i.MX28 based machine I want to have the console on &duart with > 115200 Bd, 8 Bit, no parity. > > The options for that are AFAICT: > > - use an alias, like: > > stdout-path = "serialX:115200n8"; > > the problem here is, that the duart doesn't have an alias. I guess I > shouldn't introduce a new one for my setup? > > - use a label, like: > > stdout-path = &duart, ":115200n8"; > > This would be the prettiest, but that doesn't work, because there is > a '\0' separating the path and the options. You could make that work changing the kernel parsing, but that's probably not a good option if we ever want to support more than 1 out path. > - use the full path, like: > > stdout-path = "/apb@80000000/apbx@80040000/serial@80074000:115200n8"; > > This is ugly. > > Do I miss something? Is that worth to introduce new syntax, maybe > > stdout-path = &duart . ":115200n8"; > > or similar? Seems like we should make a comma be significant in splitting strings. I'm not sure if there's anything relying on "foo" "bar" and "foo", "bar" being the same. At least for numbers, a comma has no meaning, so it would complicate the parsing I'd imagine. Not really an area I'm familiar with. Rob -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
