On 2022-11-02 23:22, Shao Miller wrote:
On 2022-10-18 19:13, Shao Miller wrote:On 2022-10-18 18:08, Chuck Silvers wrote:On Tue, Oct 18, 2022 at 08:40:54AM -0700, Shao Miller wrote:Good day, NetBSD "core." I am tinkering with porting NetBSD to: - LG Nexus 5 - Qualcomm MSM8974 Snapdragon 800 - Quad-core Krait 400 - https://wiki.lineageos.org/devices/hammerhead/A Nexus 5 variant of EFIDroid permits NetBSD's bootarm.efi ("efiboot") torun.I read that this effort ought to be announced "here" and it was implied thatI ought to ask: Is anyone else attempting the same? Thank you for your time. - Shao MillerHi Shao,I have not heard of anyone already working on this. you are pretty safeworking on a relatively old piece of arm hardware like this one. To get help with any technical questions about making NetBSD work on this hardware, or to share any progress you've made, you can use the mailing list <port-arm%netbsd.org@localhost>. Thanks! -ChuckVery well. Thanks, Chuck. - ShaoHas anyone any thoughts about a NetBSD font to use (in the kernel) with 1,080 pixels wide by 1,920 pixels high? I'm about ready to set something up in cn_tab in initarm() in sys/arch/evbarm/fdt/fdt_machdep.c - Shao Miller
Maybe this question just above was a silly one. I have a framebuffer region of memory and I have successfully drawn lines on the display from the aforementioned initarm(). Perhaps there's some way I can attach something with the name genfb in it at such an early stage, in order for early prints to work, and doing so will remove any need for me to process a font and draw it myself?
A new question: what's your favourite guide to follow for porting NetBSD to some hardware using the FDT approach? I've examined the non-FDT https://www.netbsd.org/docs/kernel/porting_netbsd_arm_soc.html article, so far.
Thank you for any time you can spare. - Shao Miller