[haiku-development] Re: 3com driver issue (Was: Terminal & VIA Rhine)
- From: "Curtis Wanner" <katisu@xxxxxxxxxxx>
- To: <haiku-development@xxxxxxxxxxxxx>
- Date: Tue, 6 Nov 2007 10:35:48 -0500
Bruno wrote:
>
> Actually, I think the "easy to port" part of Urias email was based on
> the fact that, right now, we can pretty much just get the FreeBSD
> sources for a network driver, drop it unchanged in our source tree,
> create some pretty standard glue code and the required Jamfiles and,
> voilá, it should work. Thanks to Hugo's and Axel's work in the FreeBSD
> compatibility layer porting a FreeBSD network driver should take 2
> minutes unless the driver uses something we did not foresee yet.
Yes, I'm aware of that and *perhaps* you can do that with the tulip driver.
However, from my own impression and that from previous talks with Hugo and
Travis that this is not recommended.
IMHO the driver covers too many different chipsets and in particular the
admtek chipsets should be a separate driver. Whether it would be "easy" to
use the freebsd code to do so was what I was getting at.
Anyway, bit of back seat driving on my part, do what you want.
I started on a an983b driver, but at the very least won't have it done by
end of year.
Curtis
- Follow-Ups:
- References:
- [haiku-development] Re: 3com driver issue (Was: Terminal & VIA Rhine)
- From: Urias McCullough
- [haiku-development] Re: 3com driver issue (Was: Terminal & VIA Rhine)
- From: Urias McCullough
- [haiku-development] Re: 3com driver issue (Was: Terminal & VIA Rhine)
- From: Curtis Wanner
- [haiku-development] Re: 3com driver issue (Was: Terminal & VIA Rhine)
- From: Bruno Albuquerque
Other related posts:
- » [haiku-development] Re: 3com driver issue (Was: Terminal & VIA Rhine)
- » [haiku-development] Re: 3com driver issue (Was: Terminal & VIA Rhine)
- » [haiku-development] Re: 3com driver issue (Was: Terminal & VIA Rhine)
- » [haiku-development] Re: 3com driver issue (Was: Terminal & VIA Rhine)
- » [haiku-development] Re: 3com driver issue (Was: Terminal & VIA Rhine)
- » [haiku-development] Re: 3com driver issue (Was: Terminal & VIA Rhine)
- » [haiku-development] Re: 3com driver issue (Was: Terminal & VIA Rhine)
- » [haiku-development] Re: 3com driver issue (Was: Terminal & VIA Rhine)
- » [haiku-development] Re: 3com driver issue (Was: Terminal & VIA Rhine)
- » [haiku-development] Re: 3com driver issue (Was: Terminal & VIA Rhine)
- » [haiku-development] Re: 3com driver issue (Was: Terminal & VIA Rhine)
- » [haiku-development] Re: 3com driver issue (Was: Terminal & VIA Rhine)
- » [haiku-development] Re: 3com driver issue (Was: Terminal & VIA Rhine)
- [haiku-development] Re: 3com driver issue (Was: Terminal & VIA Rhine)
- From: Urias McCullough
- [haiku-development] Re: 3com driver issue (Was: Terminal & VIA Rhine)
- From: Urias McCullough
- [haiku-development] Re: 3com driver issue (Was: Terminal & VIA Rhine)
- From: Curtis Wanner
- [haiku-development] Re: 3com driver issue (Was: Terminal & VIA Rhine)
- From: Bruno Albuquerque