search for: device_handle

...uces a code easier to follow; > specially when we end up using that handle to create a TCP4 or UDP4 child... Not all handles are devices but all usable devices have handles. The image_handle is a type EFI_LOADED_IMAGE_PROTOCOL, not a device. pxe_handle could perhaps be renamed as nic_handle or device_handle. -- -Gene

...de easier to follow; > specially when we end up using > that handle to create a TCP4 or UDP4 child... Not all handles are devices but all usable devices have handles.? The image_handle is a type EFI_LOADED_IMAGE_PROTOCOL, not a device. pxe_handle could perhaps be renamed as nic_handle or device_handle. -- -Gene <<< We already have "image_handle" that (as you say) corresponds to the EFI_LOADED_IMAGE_PROTOCOL I think that "image_DeviceHandle" would clearly represent the DeviceHandle associated to the loaded image. I use "image_DeviceHandle" in my codeb...

Thanks for the info, that is very helpful. It does look like that change got back-ported to master, albeit in a different form. I'll take a look at how OpenVPN does its windows device I/O. - todd

On Thu, Jun 25, 2015 at 7:28 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Thu, Jun 25, 2015 at 11:54 AM, Patrick Masotta <masottaus at yahoo.com> wrote: > >> Yes I know what you mean; >> "I think" the handle of the running image (our code) has a "path" telling us where >> was laded from. That would solve this thing. > > I just

...essage/i2o/i2o_block.c:324:2: error: too many arguments to function ?blk_rq_map_sg? include/linux/blkdev.h:845:12: note: declared here drivers/target/target_core_pscsi.c:1224:2: error: too many arguments to function ?__blk_put_request? include/linux/blkdev.h:645:13: note: declared here drivers/scsi/device_handler/scsi_dh_hp_sw.c:230:2: error: too many arguments to function ?__blk_put_request? include/linux/blkdev.h:645:13: note: declared here drivers/scsi/device_handler/scsi_dh_alua.c:255:2: error: too many arguments to function ?__blk_put_request? include/linux/blkdev.h:645:13: note: declared here drivers...

...essage/i2o/i2o_block.c:324:2: error: too many arguments to function ?blk_rq_map_sg? include/linux/blkdev.h:845:12: note: declared here drivers/target/target_core_pscsi.c:1224:2: error: too many arguments to function ?__blk_put_request? include/linux/blkdev.h:645:13: note: declared here drivers/scsi/device_handler/scsi_dh_hp_sw.c:230:2: error: too many arguments to function ?__blk_put_request? include/linux/blkdev.h:645:13: note: declared here drivers/scsi/device_handler/scsi_dh_alua.c:255:2: error: too many arguments to function ?__blk_put_request? include/linux/blkdev.h:645:13: note: declared here drivers...

...e available rings Marek Olšák (2): amdgpu: add amdgpu_query_sw_info for querying high bits of 32-bit address space configure.ac: bump version to 2.4.90 Michel Dänzer (7): amdgpu: Don't print error message if parse_one_line returned -EAGAIN amdgpu: Don't dereference device_handle after amdgpu_device_deinitialize amdgpu: Symlink .editorconfig to tests/amdgpu amdgpu: Disable deadlock test suite by default for SI ASICs amdgpu: Disable VM test suite by default for SI ASICs Revert "amdgpu: clean up non list code path for vamgr" amdgpu: Add...

On Tue, Feb 17, 2015 at 12:57:32PM +0100, Jur van der Burg via Syslinux wrote: > We have been using syslinux (V4.05) in our product for years without a problem. > Since we encounter more and more systems that do a UEFI boot by default > we want to support that too. So I've been using syslinux V6.03 to create > usb sticks and harddisks to allow both bios and uefi boot which works

We have been using syslinux (V4.05) in our product for years without a problem. Since we encounter more and more systems that do a UEFI boot by default we want to support that too. So I've been using syslinux V6.03 to create usb sticks and harddisks to allow both bios and uefi boot which works fine. The problem I run into now is that it is not possible to create a dvd that is capable of

...- drivers/scsi/csiostor/csio_wr.c | 2 +- drivers/scsi/cxgbi/cxgb3i/cxgb3i.c | 2 +- drivers/scsi/cxgbi/cxgb4i/cxgb4i.c | 2 +- drivers/scsi/cxlflash/main.c | 29 +++-- drivers/scsi/cxlflash/superpipe.c | 13 +- drivers/scsi/device_handler/scsi_dh_hp_sw.c | 4 +- drivers/scsi/esas2r/esas2r_flash.c | 4 +- drivers/scsi/esas2r/esas2r_init.c | 6 +- drivers/scsi/esp_scsi.c | 6 +- drivers/scsi/fcoe/fcoe_ctlr.c | 8 +- drivers/scsi/g_NCR5380.c...

...- drivers/scsi/csiostor/csio_wr.c | 2 +- drivers/scsi/cxgbi/cxgb3i/cxgb3i.c | 2 +- drivers/scsi/cxgbi/cxgb4i/cxgb4i.c | 2 +- drivers/scsi/cxlflash/main.c | 29 +++-- drivers/scsi/cxlflash/superpipe.c | 13 +- drivers/scsi/device_handler/scsi_dh_hp_sw.c | 4 +- drivers/scsi/esas2r/esas2r_flash.c | 4 +- drivers/scsi/esas2r/esas2r_init.c | 6 +- drivers/scsi/esp_scsi.c | 6 +- drivers/scsi/fcoe/fcoe_ctlr.c | 8 +- drivers/scsi/g_NCR5380.c...

...- drivers/scsi/csiostor/csio_wr.c | 2 +- drivers/scsi/cxgbi/cxgb3i/cxgb3i.c | 2 +- drivers/scsi/cxgbi/cxgb4i/cxgb4i.c | 2 +- drivers/scsi/cxlflash/main.c | 29 +++-- drivers/scsi/cxlflash/superpipe.c | 13 +- drivers/scsi/device_handler/scsi_dh_hp_sw.c | 4 +- drivers/scsi/esas2r/esas2r_flash.c | 4 +- drivers/scsi/esas2r/esas2r_init.c | 6 +- drivers/scsi/esp_scsi.c | 6 +- drivers/scsi/fcoe/fcoe_ctlr.c | 8 +- drivers/scsi/g_NCR5380.c...

...- drivers/scsi/csiostor/csio_wr.c | 2 +- drivers/scsi/cxgbi/cxgb3i/cxgb3i.c | 2 +- drivers/scsi/cxgbi/cxgb4i/cxgb4i.c | 2 +- drivers/scsi/cxlflash/main.c | 29 +++-- drivers/scsi/cxlflash/superpipe.c | 13 +- drivers/scsi/device_handler/scsi_dh_hp_sw.c | 4 +- drivers/scsi/esas2r/esas2r_flash.c | 4 +- drivers/scsi/esas2r/esas2r_init.c | 6 +- drivers/scsi/esp_scsi.c | 6 +- drivers/scsi/fcoe/fcoe_ctlr.c | 8 +- drivers/scsi/g_NCR5380.c...

...- drivers/scsi/csiostor/csio_wr.c | 2 +- drivers/scsi/cxgbi/cxgb3i/cxgb3i.c | 2 +- drivers/scsi/cxgbi/cxgb4i/cxgb4i.c | 2 +- drivers/scsi/cxlflash/main.c | 29 +++-- drivers/scsi/cxlflash/superpipe.c | 13 +- drivers/scsi/device_handler/scsi_dh_hp_sw.c | 4 +- drivers/scsi/esas2r/esas2r_flash.c | 4 +- drivers/scsi/esas2r/esas2r_init.c | 6 +- drivers/scsi/esp_scsi.c | 6 +- drivers/scsi/fcoe/fcoe_ctlr.c | 8 +- drivers/scsi/g_NCR5380.c...

Hi All, I followed the instructions here at http://bderzhavets.wordpress.com/2009/06/10/setup-fedora-11-pv-domu-at-xen-3-4-1-dom0-kernel-2-6-30-rc6-tip-on-top-of-fedora-11/ However, when I do a "make menuconfig", I cannot see any XEN related configuration options. What am I missing? Thank you. Mr. Teo En Ming Dip(Mechatronics Engineering) BEng(Hons)(Mechanical Engineering)