The 6.5 and 6.6 releases support multiboot as well - we just didn't have to have an explicit multiboot.boot file before.
 For 32 bit, you can just use the elf.boot bootfile (if you check, the 32 bit version of elf.boot and multiboot.boot are
 identical in 7.0).

The multiboot information is made available in startup via the bootregs global variable. This points to the memory 
containing the initial register values on entry to startup. You can check the bootregs->eax field for the signature 
value and then use bootregs->ebx to find the multiboot structure. What you want to do with it after that is up to you. 
The standard startup code doesn't make it available to user processes, but you can modify the board specific gear to 
pass it along if you want.

________________________________________
From: Brian Carnes(deleted) [community-noreply@qnx.com]
Sent: February-16-18 9:15 PM
To: ostech-core_os
Subject: [QNX7] QNX multiboot support and access to cmdline

We were pleased to see you that you added multiboot support to QNX7.  Thank You! (We had adapted LOADIFS for QNX6.6 for 
multiboot).

With the QNX7 multiboot facility, how does one get access to the multiboot command line passed by the loader to the QNX 
kernel?

i.e. the QNX equivalent to Linux's /proc/cmdline

for QNX multiboot, that would be when looking at the incoming multiboot record:
  flag MULTIBOOT_INFO_CMDLINE is set and then the
  NUL-terminated string pointed to by multiboot_info_t->cmdline

cf. https://www.gnu.org/software/grub/manual/multiboot/multiboot.html

Do you expose this cmdline, or the preserved raw multiboot structure, to QNX user processes?



_______________________________________________

OSTech
http://community.qnx.com/sf/go/post118592
To cancel your subscription to this discussion, please e-mail ostech-core_os-unsubscribe@community.qnx.com