From: Francois Romieu <romieu@fr.zoreil.com>
To: Tony Prisk <linux@prisktech.co.nz>
Cc: netdev@vger.kernel.org, ShirleyHu@viatech.com.cn,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
DavidLv@viatech.com.cn, AndersMa@viatech.com.cn, "Mailing List,
Arm" <linux-arm-kernel@lists.infradead.org>
Subject: Re: VIA velocity network driver
Date: Sat, 27 Apr 2013 10:53:06 +0200 [thread overview]
Message-ID: <20130427085306.GA24622@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <517B6267.4070404@prisktech.co.nz>
Tony Prisk <linux@prisktech.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
prev parent reply other threads:[~2013-04-27 8:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-27 5:30 VIA velocity network driver Tony Prisk
2013-04-27 8:53 ` Francois Romieu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130427085306.GA24622@electric-eye.fr.zoreil.com \
--to=romieu@fr.zoreil.com \
--cc=AndersMa@viatech.com.cn \
--cc=DavidLv@viatech.com.cn \
--cc=ShirleyHu@viatech.com.cn \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@prisktech.co.nz \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox