From: Stephen Hemminger <shemminger@vyatta.com>
To: "chas williams - CONTRACTOR" <chas@cmf.nrl.navy.mil>
Cc: netdev@vger.kernel.org
Subject: Re: converting fore200e driver to use request_firmware()
Date: Thu, 7 Feb 2008 11:43:17 -0800 [thread overview]
Message-ID: <20080207114317.0b9f6db1@extreme> (raw)
In-Reply-To: <200802071920.m17JKJMb029314@cmf.nrl.navy.mil>
On Thu, 07 Feb 2008 14:20:19 -0500
"chas williams - CONTRACTOR" <chas@cmf.nrl.navy.mil> wrote:
> In message <20080206.160542.07994571.davem@davemloft.net>,David Miller writes:
> >> however, i ran into a little problem with the sbus interface. what should
> >> i pass for 'struct device *' for an sbus device?
> >
> >"&sdev->ofdev.dev" should work
>
> thanks! that is what i needed. so what i have works on pci and is
> quite a bit cleaner than the current mess for the firmware. the only
> iffy part is the conversion of the struct fore_200e to a struct device
> which is depends your bus. perhaps it should be a seperate routine.
>
> any comments on the following?
>
> diff --git a/drivers/atm/Kconfig b/drivers/atm/Kconfig
> index 1c7ae30..a5303ee 100644
> --- a/drivers/atm/Kconfig
> +++ b/drivers/atm/Kconfig
> @@ -325,81 +325,21 @@ config ATM_IA_DEBUG
> speed of the driver, and the size of your syslog files! When
> inactive, they will have only a modest impact on performance.
>
> -config ATM_FORE200E_MAYBE
> +config ATM_FORE200E
> tristate "FORE Systems 200E-series"
> - depends on PCI || SBUS
> + depends on (PCI || SBUS)
> ---help---
> This is a driver for the FORE Systems 200E-series ATM adapter
> cards. It simultaneously supports PCA-200E and SBA-200E models
> on PCI and SBUS hosts. Say Y (or M to compile as a module
> named fore_200e) here if you have one of these ATM adapters.
>
> - Note that the driver will actually be compiled only if you
> - additionally enable the support for PCA-200E and/or SBA-200E
> - cards.
> -
> See the file <file:Documentation/networking/fore200e.txt> for
> further details.
>
Think you now need to select FW_LOADER?
--
Stephen Hemminger <stephen.hemminger@vyatta.com>
prev parent reply other threads:[~2008-02-07 19:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 0:01 converting fore200e driver to use request_firmware() chas williams - CONTRACTOR
2008-02-07 0:05 ` David Miller
2008-02-07 19:20 ` chas williams - CONTRACTOR
2008-02-07 19:43 ` Stephen Hemminger [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=20080207114317.0b9f6db1@extreme \
--to=shemminger@vyatta.com \
--cc=chas@cmf.nrl.navy.mil \
--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