similar to: ethersel.c32 issues

In include/sys/pci.h we have #define MAX_PCI_BUSES 255 and struct pci_bus_list { struct pci_bus pci_bus[MAX_PCI_BUSES]; uint8_t count; }; And in lib/pci/scan.c for (bus = 0; bus <= MAX_PCI_BUSES; bus++) { pci_bus_list->pci_bus[bus].pci_device_count = 0; Fix possible overflows and introduce MAX_PCI_FUNC. - Sebastian Index: syslinux-20080611/com32/lib/pci/scan.c

Hello! ethersel.c32 does not seem to work with all PCs. I have prepared a floppy that uses ethersel.c32 to load a NIC-specific file (etherboot .zlilo image). See http://etherboot.anadex.de for details. It works with every NIC and every PC I own, but not with VMWare. I know VMWare has some problems, so that did not bother me at all and I published it anyway but I have received several e-mails

From : Erwan Velu <erwan.velu at free.fr> This patch - remove the pci detection code from ethersel - add a find_pci_device() function in the PCI com32 module - make ethersel using the pci com32 module instead of builtin pci detection code Testing and feedback are welcome. Signed-off-by:Erwan Velu <erwan.velu at free.fr> -------------- next part -------------- A non-text attachment

Replace get_config() and execute() with syslinux_config_file() and syslinux_run_command(). - Sebastian Index: syslinux-3.71-pre14-8-gb8f5d7d/com32/modules/ethersel.c =================================================================== --- syslinux-3.71-pre14-8-gb8f5d7d.orig/com32/modules/ethersel.c 2008-07-18 19:45:15.000000000 +0200 +++ syslinux-3.71-pre14-8-gb8f5d7d/com32/modules/ethersel.c

Got the following trying to build git master: gcc -std=gnu99 -m32 -fno-stack-protector -mregparm=3 -DREGPARM=3 -march=i386 -Os -W -Wall -march=i386 -fomit-frame-pointer -D__COM32__ -nostdinc -iwithprefix include -I../../com32/libutil/include -I../../com32/include -c -o chain.o chain.c ld -m elf_i386 -T ../../com32/lib/com32.ld -o chain.elf chain.o ../../com32/libutil/libutil_com.a

Hi, I am trying to run solaris 10 (9/10) on Xen 3.4 (centos5.5 as dom0) in HVM mode. I can see the realtek 8139 network adapters when I do pciscan but ''ifconfig -a'' just lists loopback device. I can load rtls drivers but still these realtek interfaces are not available. I found a link which does say The rtls driver from Realtek still uses version 0 interfaces that are now

Hello! I have been successful using SYSLINUX and Etherboot to create a generic "PXE-on-a-disk" package, a floppy image and CD image that support as many Ethernet cards as possible. These have support for all of Etherboot's modules that support real PCI cards: about 25-or-so drivers and 250-or-so cards. I've built Etherboot ZLILO images, one for each driver, set up to boot

This patch adds a 'raid' interface class. It is basically a clone of the existing 'scsi' interface, only allowing up to 128 disks. Signed-off-by: Hannes Reinecke <hare at suse.de> --- hw/pc.c | 5 +++++ hw/pci-hotplug.c | 1 + hw/scsi-disk.c | 17 +++++++++++++++++ hw/scsi-disk.h | 20 +++++++++++++++++++- qemu-config.c | 2 +- sysemu.h

This patch adds a 'raid' interface class. It is basically a clone of the existing 'scsi' interface, only allowing up to 128 disks. Signed-off-by: Hannes Reinecke <hare at suse.de> --- hw/pc.c | 5 +++++ hw/pci-hotplug.c | 1 + hw/scsi-disk.c | 17 +++++++++++++++++ hw/scsi-disk.h | 20 +++++++++++++++++++- qemu-config.c | 2 +- sysemu.h

Support SR-IOV capability. By default, this feature is not enabled and the SR-IOV device behaves as traditional PCI device. After it's enabled, each Virtual Function's PCI configuration space can be accessed using its own Bus, Device and Function Number (Routing ID). Each Virtual Function also has PCI Memory Space, which is used to map its own register set. Signed-off-by: Yu Zhao

Support SR-IOV capability. By default, this feature is not enabled and the SR-IOV device behaves as traditional PCI device. After it's enabled, each Virtual Function's PCI configuration space can be accessed using its own Bus, Device and Function Number (Routing ID). Each Virtual Function also has PCI Memory Space, which is used to map its own register set. Signed-off-by: Yu Zhao

Support SR-IOV capability. By default, this feature is not enabled and the SR-IOV device behaves as traditional PCI device. After it's enabled, each Virtual Function's PCI configuration space can be accessed using its own Bus, Device and Function Number (Routing ID). Each Virtual Function also has PCI Memory Space, which is used to map its own register set. Signed-off-by: Yu Zhao

I released a new prerelease for SYSLINUX which supports PCI BIOS access for ethersel.c32. If you've had trouble with ethersel.c32, I would appreciate it if you'd test it out. http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/ Thanks, -hpa

Changes in 3.10: * gcc 4.0.1 compilation fixes. * Add support for querying the PCI BIOS in libcom32 (used by ethersel et al.) * Fix PCI handing (ethersel etc) on several old chipsets (and VMWare.) * Try to deal with systems with broken EBIOS. * New API call to do "localboot". * New API call to query features.

Tying up lose ends, and adding the ethersel module for the Etherboot folks. -hpa Changes in 3.02: * SYSLINUX: The "unix" installer now sets the MS-DOS attributes (hidden, system, readonly.) * COM32 library: build the .lnx (test modules for running under Linux) as architecture native modules, in case i386 devel libraries aren't

On Sun, Sep 20, 2015 at 8:33 AM, syslinux-bot for Gene Cumm <gene.cumm at gmail.com> wrote: > Commit-ID: e0ac1d2fdf7d7c58457f3796a12561cce95ca29f > Gitweb: http://www.syslinux.org/commit/e0ac1d2fdf7d7c58457f3796a12561cce95ca29f > Author: Gene Cumm <gene.cumm at gmail.com> > AuthorDate: Sun, 20 Sep 2015 08:30:55 -0400 > Committer: Gene Cumm <gene.cumm at

[PATCH 3/4] PCI: support SR-IOV capability Support SR-IOV capability. By default, this feature is not enabled and the Physical Function behaves as normal PCIe device. After it's enabled, each Virtual Function's PCI configuration space can be accessed using its own Bus, Device and Function Number (Routing ID). Each Virtual Function also has PCI Memory Space, which is used to map its own

[PATCH 3/4] PCI: support SR-IOV capability Support SR-IOV capability. By default, this feature is not enabled and the Physical Function behaves as normal PCIe device. After it's enabled, each Virtual Function's PCI configuration space can be accessed using its own Bus, Device and Function Number (Routing ID). Each Virtual Function also has PCI Memory Space, which is used to map its own

[PATCH 3/4] PCI: support SR-IOV capability Support SR-IOV capability. By default, this feature is not enabled and the Physical Function behaves as normal PCIe device. After it's enabled, each Virtual Function's PCI configuration space can be accessed using its own Bus, Device and Function Number (Routing ID). Each Virtual Function also has PCI Memory Space, which is used to map its own

Changes in 3.11: * MEMDISK: Fix bug by which accessing the real floppy disk as B: in MS-DOS was broken. * Simple menu system: allow tweaking of the screen layout. * Simple menu system: better command-line editing, correctly handle command lines above 256 characters. * PXELINUX: revert memory allocation change that caused problems