by summers » Sat Dec 26, 2020 11:16 am
Yes the only think I could see that was serial related, was the 8250. Not sure what you can set in 8250_core ...
Anyway I'm drawing a blank on debugging the kernel, or rather its looking a tad painful.
My gut feeling is we are getting to the stage of contacting Radu Pirea. Not sure how well known his email is, but it on the linux github for the atmel serial driver. Anyway may be worth contacting him, saying your serial doesn't come up, exactly your machine, and kernel; and that you are using the stock linux device tree for your board.
Radu may or may not be able to help - e.g. if he just gets too much email, may not get a reply. Also his reply may well be changes to make to the kernel, and so you'll have to compile from scratch. So best if you are happy with this.
Anyway its hard to see how else to make progress, you don't seem to be be doing anything obviously wrong, and its quite confusing.
Oh yes, thought some more about pocket beagle and your use case of adding wi-fi. The click boards that the pocket beagle uses, just use the inner row of pins, and that just gives power and serial interfaces (UART/i2c/SPI) and these aren't natural for a network adaptor, like wi-fi, which would ideally go via usb. The pocket beagle does have usb, on the outside row of pins. So that would be where to do wi-fi. Alas don't think there are any ready to use boards for that on the pocket beagle, so would need someone to do the wiring themselves. Also this would loose the beauty of the beagle family, that it has pins on both sides - and ideally daughter boards plug into both side. This makes the daughter board very stable.
Guess I should look and see what people are doing with the pocket beagle, seems rarely mentioned. I got one of the first released, and used it to get arch arm working on it. Now I just use it as my main armv7 board, so for developing any software that I work on. E.g. its currently half way through doing modern uboot for kirkwood devices ...