Hi Mika, Mika Westerberg <mika.westerberg@xxxxxxxxxxxxxxx> wrote on Fri, 27 Mar 2020 18:48:02 +0200: > On Fri, Mar 27, 2020 at 05:19:07PM +0100, Miquel Raynal wrote: > > Hi Mika, > > > > Mika Westerberg <mika.westerberg@xxxxxxxxxxxxxxx> wrote on Fri, 27 Mar > > 2020 17:56:08 +0200: > > > > > Hi, > > > > > > I don't think it is good idea to change PCI device name like that. > > > > > > Instead the MTD cmdline parser should be teach to handle names like this > > > properly. > > > > It is a bit more complicated than that since parsers have been using > > this syntax for a long time and, more importantly, it means > > potentially updating all bootloaders. > > > > I am not against updating the parser, but the s/:/|/ solution proposed > > before is rather undescriptive and it is hard to find an alternative > > character that would have a meaning here. > > I'm completely unfamiliar with these but would escape char work here? I > mean if you want ":" to be parsed literally then you pass "\:" in the > command line. That should work with the existing and also allow > supporting SPI NOR controllers on PCI bus. We would still have to update bootloaders code but that would be easy to handle. The logic being "search for the next ':', when you have one check if there is a '\' in front of it. If yes, search again". Why not... This also means reconstructing the name by dropping manually the additional '\' in Linux. Thanks, Miquèl ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/