This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.
Andreas.Eversberg Andreas.Eversberg at versatel.deboth subdevices: b553 and b523 are already part of the driver. { PCI_VENDOR_ID_CCD, PCI_DEVICE_ID_CCD_HFCE1, PCI_VENDOR_ID_CCD, PCI_SUBDEVICE_ID_CCD_IOB1E1, 0, 0, H(24)}, /* IOB1E1 */ { PCI_VENDOR_ID_CCD, PCI_DEVICE_ID_CCD_HFCE1, PCI_VENDOR_ID_CCD, PCI_SUBDEVICE_ID_CCD_JHSE1, 0, 0, H(25)}, /* Junghanns E1 */ please check definitions. PCI_SUBDEVICE_ID_CCD_IOB1E1 should be b523 and PCI_SUBDEVICE_ID_CCD_JHSE1 should be b553. (do a grep onto your repository (grep b523 <path>/* -r) -----Ursprüngliche Nachricht----- Von: openbsc-bounces at lists.gnumonks.org [mailto:openbsc-bounces at lists.gnumonks.org] Im Auftrag von Harald Welte Gesendet: Mittwoch, 19. August 2009 18:08 An: dexter Cc: openbsc at lists.gnumonks.org Betreff: Re: Problems with HFC-E1 card (Unknown HFC multiport controller) On Mon, Aug 17, 2009 at 08:24:50PM +0200, dexter wrote: > Here is an output from a linux box that works with the other card: > Unknown HFC multiport controller (vendor:1397 device:30b1 > subvendor:ffffffff subdevice:ffffffff) Please contact the driver > maintainer for support. Hi, I think you should report this to the misdn development list. as a quick workaround, I suggesty you add the pci vendor / device ID to the hfcmulti.c driver (hfcmulti_probe() would be the case). What particular HFC-E1 card is this? At least according to my kernel, PCI_VENDOR_ID_CCD is 0x1397 PCI_DEVICE_ID_CCD_HFCE1 is 0x30b1 so I don't know why you get that message... -- - Harald Welte <laforge at gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)