On Wed, Sep 19, 2018 at 03:58:56PM +0200, Daniel Kiper wrote:
> On Thu, Sep 06, 2018 at 08:02:02PM +0200, Mihai Moldovan wrote:
> > * On 09/06/2018 07:36 PM, Vladimir 'phcoder' Serbinenko wrote:
> > > Grub partition get start returns in 512B blocks. Can I have more details
> > > like
> > > which p
On Thu, Sep 06, 2018 at 08:02:02PM +0200, Mihai Moldovan wrote:
> * On 09/06/2018 07:36 PM, Vladimir 'phcoder' Serbinenko wrote:
> > Grub partition get start returns in 512B blocks. Can I have more details
> > like
> > which partmap you use?
>
> Yes, but this is a low-level function that expects s
* On 09/06/2018 07:36 PM, Vladimir 'phcoder' Serbinenko wrote:
> Grub partition get start returns in 512B blocks. Can I have more details like
> which partmap you use?
Yes, but this is a low-level function that expects sector sizes in HW sector
addressing mode.
Note that the whole sector convers
Grub partition get start returns in 512B blocks. Can I have more details
like which partmap you use?
On Mon, 23 Jul 2018, 09:54 Mihai Moldovan, wrote:
> When reading data off a disk, sector values are based on the disk sector
> length.
>
> Within grub_util_fd_open_device(), the start of the part
On Mon, Jul 23, 2018 at 08:52:50AM +0200, Mihai Moldovan wrote:
> When reading data off a disk, sector values are based on the disk sector
> length.
>
> Within grub_util_fd_open_device(), the start of the partition was taken
> directly from grub's partition information structure, which uses the
> i
When reading data off a disk, sector values are based on the disk sector
length.
Within grub_util_fd_open_device(), the start of the partition was taken
directly from grub's partition information structure, which uses the
internal sector length (currently 512b), but never transformed to the
disk's
