On Thu, Apr 28, 2011 at 04:11:11PM +0200, Arun Thomas wrote:
The multiboot info struct's 'boot_device' field has 'part1' set to 0x01, which
maps to the second primary partition. To specify the first primary partition,
'part1' should be set to 0x00, since partition numbers start from zero
On Wed, May 18, 2011 at 11:49:26PM +0200, Arun Thomas wrote:
On Sun, May 1, 2011 at 6:35 PM, Stefan Hajnoczi stefa...@gmail.com wrote:
On Thu, Apr 28, 2011 at 3:11 PM, Arun Thomas arun.tho...@gmail.com wrote:
The multiboot info struct's 'boot_device' field has 'part1' set to 0x01,
which
On Sun, May 1, 2011 at 6:35 PM, Stefan Hajnoczi stefa...@gmail.com wrote:
On Thu, Apr 28, 2011 at 3:11 PM, Arun Thomas arun.tho...@gmail.com wrote:
The multiboot info struct's 'boot_device' field has 'part1' set to 0x01,
which
maps to the second primary partition. To specify the first primary
On Thu, Apr 28, 2011 at 3:11 PM, Arun Thomas arun.tho...@gmail.com wrote:
The multiboot info struct's 'boot_device' field has 'part1' set to 0x01, which
maps to the second primary partition. To specify the first primary partition,
'part1' should be set to 0x00, since partition numbers start
The multiboot info struct's 'boot_device' field has 'part1' set to 0x01, which
maps to the second primary partition. To specify the first primary partition,
'part1' should be set to 0x00, since partition numbers start from zero
according to the multiboot spec.
Signed-off-by: Arun Thomas
