Re: [ipxe-devel] iPXE on multiple chips with the same PCI ID

2017-01-02 Thread Robin Smidsrød
I think you might need a ISA ROM instead of a PCI ROM, because the ISA
ROM usually enumerates all known/supported adapters.

-- Robin

On 28.12.2016 15.24, Аладышев Константин wrote:
> I have a board with multiple external PCIe Ethernet I350 chips.
> 
> In my lspci I have:
> 03.00.0 (4-port I350)
> 03.00.1
> 03.00.2
> 03.00.3
> 04.00.0 (4-port I350)
> 04.00.1
> 04.00.2
> 04.00.3
> 05.00.0 (2-port I350)
> 05.00.1
> 
> I builtin iPXE image to coreboot and I have all of these devices in Seabios
> bootmenu.
> But the problem is that I can only boot from ports of the first appeared
> chip. In the example above it will be 03.00.x boot devices. If I'll
> physically unplug 03.00.x chip, I'll be able to boot from 04.00.x boot
> devices. And if I'll unplug 03.00.x and 04.00.x chip, I'll be able to boot
> from 05.00.x boot devices.
> 
> Is there any such limitation in iPXE, does someone had the same problem and
> is there any idea of how to solve it? 
> 
> Coreboot+SeaBIOS log is in attachment (it has some additional printk's)
> 
> 
> ___
> ipxe-devel mailing list
> ipxe-devel@lists.ipxe.org
> https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
> 
___
ipxe-devel mailing list
ipxe-devel@lists.ipxe.org
https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel


Re: [ipxe-devel] iPXE on multiple chips with the same PCI ID

2016-12-29 Thread Christian Nilsson
How did you build ipxe and how did you include it into Coreboot build?
Also is this pcbios mode or EFI mode?
The idea is that you should have a "separate rom" for each device,
however that depends on the build and on how ipxe get's loaded

On Wed, Dec 28, 2016 at 3:24 PM, Аладышев Константин
 wrote:
> I have a board with multiple external PCIe Ethernet I350 chips.
>
> In my lspci I have:
> 03.00.0 (4-port I350)
> 03.00.1
> 03.00.2
> 03.00.3
> 04.00.0 (4-port I350)
> 04.00.1
> 04.00.2
> 04.00.3
> 05.00.0 (2-port I350)
> 05.00.1
>
> I builtin iPXE image to coreboot and I have all of these devices in Seabios
> bootmenu.
> But the problem is that I can only boot from ports of the first appeared
> chip. In the example above it will be 03.00.x boot devices. If I'll
> physically unplug 03.00.x chip, I'll be able to boot from 04.00.x boot
> devices. And if I'll unplug 03.00.x and 04.00.x chip, I'll be able to boot
> from 05.00.x boot devices.
>
> Is there any such limitation in iPXE, does someone had the same problem and
> is there any idea of how to solve it?
>
> Coreboot+SeaBIOS log is in attachment (it has some additional printk's)
>
>
> ___
> ipxe-devel mailing list
> ipxe-devel@lists.ipxe.org
> https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
___
ipxe-devel mailing list
ipxe-devel@lists.ipxe.org
https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel