search for: edd_param

...ct disk *bios_disk_init(void *privat /* Get EBIOS support */ ireg.eax.b[1] = 0x41; ireg.ebx.w[0] = 0x55aa; - ireg.eflags.b[0] = 0x3; /* CF set */ + ireg.edx.b[0] = devno; __intcall(0x13,&ireg,&oreg); @@ -353,6 +353,7 @@ struct disk *bios_disk_init(void *privat edd_params.len = sizeof edd_params; ireg.eax.b[1] = 0x48; + ireg.edx.b[0] = devno; ireg.ds = SEG(&edd_params); ireg.esi.w[0] = OFFS(&edd_params); __intcall(0x13,&ireg,&oreg);

...sk_init(void *privat /* Get EBIOS support */ ireg.eax.b[1] = 0x41; ireg.ebx.w[0] = 0x55aa; + ireg.edx.b[0] = devno; ireg.eflags.b[0] = 0x3; /* CF set */ __intcall(0x13, &ireg, &oreg); @@ -353,6 +354,7 @@ struct disk *bios_disk_init(void *privat edd_params.len = sizeof edd_params; ireg.eax.b[1] = 0x48; + ireg.edx.b[0] = devno; ireg.ds = SEG(&edd_params); ireg.esi.w[0] = OFFS(&edd_params); __intcall(0x13, &ireg, &oreg); --- On 22.02.2014 16:59, Geert Stappers wrote: > Op 2014-02-20...

...legacy_heads", info.legacy_max_head + 1); + SET_TABLE_STRING_INT(L, "legacy_cylinders", info.legacy_max_cylinder + 1); + SET_TABLE_STRING_INT(L, "legacy_sectors_per_track", + info.legacy_sectors_per_track + 1); + // edd + SET_TABLE_STRING_INT(L, "info", info.edd_params.info); + SET_TABLE_STRING_INT(L, "cylinders", info.edd_params.cylinders); + SET_TABLE_STRING_INT(L, "heads", info.edd_params.heads); + SET_TABLE_STRING_INT(L, "sectors", info.edd_params.sectors); + // size in mb as lua number type is uint32_t + SET_TABLE_STRING_I...

...t understand where the removal of that line matches with 'DL register is not set' from the description of this patch. > + ireg.edx.b[0] = devno; > > __intcall(0x13,&ireg,&oreg); > > @@ -353,6 +353,7 @@ struct disk *bios_disk_init(void *privat > edd_params.len = sizeof edd_params; > > ireg.eax.b[1] = 0x48; > + ireg.edx.b[0] = devno; > ireg.ds = SEG(&edd_params); > ireg.esi.w[0] = OFFS(&edd_params); > __intcall(0x13,&ireg,&oreg); > Groeten Geert Stappers -- Leven en laten l...

Hi, Hopefully you someone can tell me what I'm doing wrong. First, the code. I placed this at the bottom of the main loop in com32/modules/disk.c as a simple test of writing to the disk: printf(" Host bus: %s, Interface type: %s\n\n", d->edd_params.host_bus_type, d->edd_params.interface_type); zero_buf = calloc(1, d->edd_params.bytes_per_sector); for(int sector = 0; sector < d->edd_params.sectors; sector++){ err = write_verify_sectors(d, sector,zero_buf,1); if (err == -1) { printf("sector: %d error: %d\n", s...

...ze / disk->sector_size; - - disk->rdwr_sectors(disk, buf, block * sec_per_block, sec_per_block, 0); + rdwr_bytes(disk, buf, (bytes_t)block * block_size, block_size, 0); } @@ -373,6 +445,8 @@ struct disk *disk_init(uint8_t devno, bool cdrom, sector_t part_start, is_power_of_2(edd_params.sector_size)) sector_size = edd_params.sector_size; } + if (hard_max_transfer > (0x10000/sector_size)) + hard_max_transfer = (0x10000/sector_size); } } diff --git a/core/fs/ext2/ext2.c b/core/fs/ext2/ext2.c index 716670c..bddde8d 100644 --- a/core/fs/ext2/ext2.c +++ b...

...r_sectors(struct disk *disk, void *buf, struct disk *bios_disk_init(void *private) { - static struct disk disk; + struct disk *disk; struct bios_disk_private *priv = (struct bios_disk_private *)private; com32sys_t *regs = priv->regs; static __lowmem struct edd_disk_params edd_params; @@ -302,6 +302,10 @@ struct disk *bios_disk_init(void *private) int sector_size; unsigned int hard_max_transfer; + disk = malloc(sizeof(struct disk)); + if (!disk) + return NULL; + memset(&ireg, 0, sizeof ireg); ireg.edx.b[0] = devno; @@ -319,18 +323,18 @@ s...

This set of patches add some support for sector size >512. Currently it fixes extlinux, MBR for GPT and ext partitions. Other code is unaffected. This set of patches has been tested on a read Dell machine running a beta firmware.

..._parameters_with_extensions(struct driveinfo *drive_info) __intcall(0x13, &inreg, &outreg); /* CF set on error */ - if (outreg.eflags.l & EFLAGS_CF) + if (outreg.eflags.l & EFLAGS_CF) { + lfree(dp); return outreg.eax.b[1]; + } memcpy(&drive_info->edd_params, dp, sizeof drive_info->edd_params); + lfree(dp); return 0; } diff --git a/com32/gpllib/disk/read.c b/com32/gpllib/disk/read.c index 7a6cc43..541957f 100644 --- a/com32/gpllib/disk/read.c +++ b/com32/gpllib/disk/read.c @@ -76,13 +76,22 @@ int read_sectors(struct driveinfo *drive_info...

From: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> Hi all, This series adds a new microcode driver for Xen. The Xen hypervisor can deal with all the low-level details of doing a microcode update (Intel vs AMD, doing all the physical CPUs present on the system, current and future, etc), so all the driver has to do is make a hypercall to upload the microcode into Xen. This only

From: Matt Fleming <matt.fleming at linux.intel.com> This series fixes some bugs and switches the elflink branch to be entirely ELF modules. It applies on top of, http://syslinux.zytor.com/archives/2011-April/016369.html The deletions in the diff stat below are mainly from deleting com32/elflink/modules (finally!). Now there should be no duplicate code because we don't need COM32 and

Hello, the following patches should get multidisk access working. The syntax accepted is the following: (hdx,y)/path/to/file where x is the disk number and start at 0 and the y is the partition number starting at 1. So (hd0,1) is the first partition of the first disk. the other accepted syntax is using MBR's 32 bits disk signature so for example: (mbr:0x12345678,2)/foo/bar would address

So last week I was wondering if XFS was still working -- even with its last on-disk structure changes -- and it _suprisingly_ worked as expected. Right, now I can finally get rid of GRUB and use Syslinux to boot my Linux on EFI from a rootfs with xfs. Shit, I have two partitions (the first one being the required ESP) so there is no way to access the other partitions since because Syslinux does not

Hi Ingo, Here''s the chunk of patches to add Xen Dom0 support (it''s probably worth creating a new xen/dom0 topic branch for it). A dom0 Xen domain is basically the same as a normal domU domain, but it has extra privileges to directly access hardware. There are two issues to deal with: - translating to and from the domain''s pseudo-physical addresses and real machine