>
> > Okay, I get that and it makes sense with what I know so far about how
the
> > kernel device model works (which I'm still learning). So how would I
> > manually add a device? Say I create the PCI wrapper driver that
claims
> > the clone-TSEC, is there a "register device" type call simi
On Tue, 4 Jan 2011 13:00:07 -0800
bruce_leon...@selinc.com wrote:
> True, but we really didn't want to recreate all the infrastructure
> that the gianfar driver has in it we wanted to just use it. Maybe
> what I should do is just take the guts of the gianfar driver and make
> a pure PCI driver ou
On Tue, 4 Jan 2011 13:00:07 -0800
wrote:
> Okay, I get that and it makes sense with what I know so far about how the
> kernel device model works (which I'm still learning). So how would I
> manually add a device? Say I create the PCI wrapper driver that claims
> the clone-TSEC, is there a "r
On Tue, 2011-01-04 at 13:23 -0600, Scott Wood wrote:
> On Tue, 4 Jan 2011 10:58:35 -0800
> wrote:
>
> > Hi all,
> >
> > I'm working on a project with an MPC8347 and three ethernet ports. Because
> > of end of life issues we've had to replace the part we're using for the
> > third ethernet port
Scott,
Thanks for the feedback.
>
> Making a faithful clone of any reasonably complex device strikes me as
> more work than writing a new ethernet driver.
>
> The last thing you want to end up doing is...
>
> > And for speed sake it would go on the PCI bus.
> > (So much for letting HW make d
On Tue, 4 Jan 2011 10:58:35 -0800
wrote:
> Hi all,
>
> I'm working on a project with an MPC8347 and three ethernet ports. Because
> of end of life issues we've had to replace the part we're using for the
> third ethernet port and we decided rather than rely on a vendor who would
> pull a part
