lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 27 Apr 2013 10:53:06 +0200 From: Francois Romieu <romieu@...zoreil.com> To: Tony Prisk <linux@...sktech.co.nz> Cc: "Mailing List, Arm" <linux-arm-kernel@...ts.infradead.org>, netdev@...r.kernel.org, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, DavidLv@...tech.com.cn, ShirleyHu@...tech.com.cn, AndersMa@...tech.com.cn Subject: Re: VIA velocity network driver Tony Prisk <linux@...sktech.co.nz> : > I would like to add support to this driver for platform devices as > found on VIA's APC8750 board. At the moment, I have a standalone > platform version that works fine, but wanted to ask a few questions > before sending a patch to merge this code into one driver. > > The current driver is for PCI network cards, and uses pci dma > functions. Most of the pci dma functions are wrappers around other > functions which is what I have used for the platform version. [...] > Is it ok to use the non-pci versions (which are basically just the > unwrapped pci versions) and pass the struct device *, or will I need > to use the correct function for the correct instance. It's ok. A standalone patch to convert the pci dma functions and check the returned status code of the new one would be welcome regardless of any future change in the driver data struct. [...] > I assume this is loading something from an EEPROM, but there is no > EEPROM on the APC8750. Removing this code, the driver seems to work > fine on the APC8750. I feel a "no documentation" disturbance in the force. Via's people Cced. > Could it be avoided with a vptr->has_no_eeprom that defaults to 0 to > avoid breaking existing support? Yes. No unnecessary module option please. -- Ueimor -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists