search for: device_handler

Displaying 15 results from an estimated 15 matches for "device_handler".

2015 Jun 27
2
EFI: PXE: "My IP is 0.0.0.0"
On Fri, Jun 26, 2015 at 10:49 AM, Patrick Masotta <masottaus at yahoo.com> wrote: >>>> > Commit 23b2707 should resolve this. Please > let me know if you need > test binaries > > -- > -Gene > <<< > > > 1) About the Service Binding protocols, PXE protocol, etc having the same handle# is clear if we > see that the number is in fact
2015 Jun 27
0
EFI: PXE: "My IP is 0.0.0.0"
>>> It's a handle to the device that loaded Syslinux, in this case a NIC plus IP-stack (IPv4 or IPv6). <<< Yes it is the handle of the device (NIC) that loaded syslinux plus IP stack (as you said) but also all the attached Service Binding Protocols, PXE Protocol, and some more. All of them sharing the same device handle. >>> > 2.2) > I think
2018 Jan 16
3
Windows TAP driver issues
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
2015 Jun 26
2
EFI: PXE: "My IP is 0.0.0.0"
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
2012 Jun 13
2
drivers/block/cpqarray.c:938:2: error: too many arguments to function ‘blk_rq_map_sg’
...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/...
2012 Jun 13
2
drivers/block/cpqarray.c:938:2: error: too many arguments to function ‘blk_rq_map_sg’
...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/...
2018 Feb 17
0
[ANNOUNCE] libdrm 2.4.90
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Andrey Grodzovsky (2): amdgpu: Update deadlock test to not assert on ECANCELED amdgpu: Fix segfault in deadlock test. Anuj Phogat (1): intel: Add more Coffeelake PCI IDs Bas Nieuwenhuizen (1): drm: Fix 32-bit drmSyncobjWait. Christian König (5): amdgpu: fix 32bit VA manager max address headers: sync up
2015 Feb 18
0
uefi and bios bootable optical media
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
2015 Feb 17
4
uefi and bios bootable optical media
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
2020 Mar 11
0
[PATCH -next 000/491] treewide: use fallthrough;
...- 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 |...
2020 Mar 11
0
[PATCH -next 000/491] treewide: use fallthrough;
...- 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 |...
2020 Mar 11
0
[PATCH -next 000/491] treewide: use fallthrough;
...- 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 |...
2020 Mar 11
0
[PATCH -next 000/491] treewide: use fallthrough;
...- 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 |...
2020 Mar 11
0
[PATCH -next 000/491] treewide: use fallthrough;
...- 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 |...
2009 Jul 22
109
Unable to Configure Xen Dom 0 in Jeremy''s PVOPS Kernel
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)