Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 104709 - zd1201 and zd1201-firmware work on amd64
Summary: zd1201 and zd1201-firmware work on amd64
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: AMD64 Linux
: High enhancement (vote)
Assignee: AMD64 Project
URL:
Whiteboard:
Keywords:
: 111245 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-09-03 06:16 UTC by Kamil Rytarowski
Modified: 2006-09-17 15:41 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kamil Rytarowski 2005-09-03 06:16:10 UTC
wireless drivers "zd1201" and "zd1201-firmware" are stable on amd64

Reproducible: Always
Steps to Reproduce:
1.
2.
3.



Expected Results:  
add "amd64" flag to ebuilds
Comment 1 Jim Laflin 2005-09-03 07:19:46 UTC
Can't mark stable until they've been ~amd64 for at least 30 days. Changing summary

I don't have this hardware unfortunately so am unable to test atm

Jim
Comment 2 Steff 2005-10-02 06:47:45 UTC
"zd1201-firmware" stable on amd64 for me too!
I did not use "zd1201" as the driver is present in gentoo-sources-2.6.12-r10
Comment 3 Simon Stelling (RETIRED) gentoo-dev 2005-10-04 14:16:19 UTC
we're currently testing a new alias system, sorry for the bugspam
Comment 4 Simon Stelling (RETIRED) gentoo-dev 2006-02-19 00:35:01 UTC
*** Bug 111245 has been marked as a duplicate of this bug. ***
Comment 5 Simon Stelling (RETIRED) gentoo-dev 2006-02-19 00:35:06 UTC
*** Bug 119472 has been marked as a duplicate of this bug. ***
Comment 6 Stéphane Bisinger 2006-02-19 09:38:57 UTC
I'm wondering why bug #119472 has been marked duplicate of this bug, we're talking about two different drivers: here is zd1201, my bug is about zd1211. Even if similar, they are unrelated and they apply to completely different devices. (And two different modules)
Comment 7 Simon Stelling (RETIRED) gentoo-dev 2006-02-19 09:48:32 UTC
sorry, missed that -> reopened
Comment 8 Alberto Bertogli 2006-07-25 19:41:28 UTC
(In reply to comment #2)
> "zd1201-firmware" stable on amd64 for me too!
> I did not use "zd1201" as the driver is present in gentoo-sources-2.6.12-r10

I confirm that the firmware ebuild works a expected on amd64 (Pentium D 850).

I didn't test the driver as I use the one provided with the kernel.org sources.
Comment 9 Danny van Dyk (RETIRED) gentoo-dev 2006-07-29 01:59:44 UTC
zd1201 firmware isn't even marked ~amd64!
Simon: I'm inclined to close this one, unless some AT or dev with a zd1201
based wlan card/key comes up.
Comment 10 Alberto Bertogli 2006-07-29 04:34:47 UTC
(In reply to comment #9)
> zd1201 firmware isn't even marked ~amd64!

I marked it ~amd64 in my local overlay. It works fine.


> Simon: I'm inclined to close this one, unless some AT or dev with a zd1201
> based wlan card/key comes up.

So you won't mark the firmware ~amd64?
Comment 11 Simon Stelling (RETIRED) gentoo-dev 2006-07-29 07:54:18 UTC
Danny:

In the past, we've always followed the 'if nobody has the hardware just look whether it merges or not and trust the user for everything else' rule. Why not here?
Comment 12 Jason Huebel (RETIRED) gentoo-dev 2006-09-17 09:57:39 UTC
I agree. Since more than one user has reported success, I'd say we could at least get away with marking this ~amd64. The practical fact of the matter is that we'll never have access to every single piece of hardware needed to personally test these bugs.

I do have one concern though. We don't have any documentation showing the user's setup.  Documenting their "emerge --info" would be a good idea at the very least. That way we can verify kernel version and that they are indeed running in 64-bit mode.
Comment 13 Jason Huebel (RETIRED) gentoo-dev 2006-09-17 11:32:53 UTC
marked ~amd64
Comment 14 Alberto Bertogli 2006-09-17 15:41:24 UTC
(In reply to comment #12)
> I agree. Since more than one user has reported success, I'd say we could at
> least get away with marking this ~amd64. The practical fact of the matter is
> that we'll never have access to every single piece of hardware needed to
> personally test these bugs.

Thanks a lot for bringing some common sense into this =)


> I do have one concern though. We don't have any documentation showing the
> user's setup.  Documenting their "emerge --info" would be a good idea at the
> very least. That way we can verify kernel version and that they are indeed
> running in 64-bit mode.

Sure. Here's mine. As I said earlier (almost two months ago), I only use the firmware, because the in-kernel driver works fine for me.


I've tested it with several kernels, and the firmware always worked as expected.

# emerge --info
Portage 2.1 (default-linux/amd64/2006.0, gcc-4.1.1, glibc-2.4-r3, 2.6.18-rc6 x86_64)
=================================================================
System uname: 2.6.18-rc6 x86_64 Intel(R) Pentium(R) D CPU 3.00GHz
Gentoo Base System version 1.12.4
ccache version 2.3 [enabled]
app-admin/eselect-compiler: [Not Present]
dev-lang/python:     2.3.5, 2.4.2
dev-python/pycrypto: 2.0.1-r5
dev-util/ccache:     2.3
dev-util/confcache:  [Not Present]
sys-apps/sandbox:    1.2.11
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils:  2.17
sys-devel/gcc-config: 1.3.13-r2
sys-devel/libtool:   1.5.18-r1
virtual/os-headers:  2.6.16
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-O2 -march=nocona -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config"
CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c"
CXXFLAGS="-O2 -march=nocona -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig ccache distlocks metadata-transfer parallel-fetch sandbox sfperms strict"
GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo"
LC_ALL="en_US.utf8"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage /usr/local/overlays/xgl-overlay"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="amd64 X aac alsa avi bash-completion bash_completion berkdb bitmap-fonts bzip2 cairo cdr cli crypt dbus dga dlloader dri dts dvd dvdr dvdread eds emboss encode fastcgi flac foomaticdb gcj gif gpm gstreamer gtk gtk2 imlib input_devices_keyboard input_devices_mouse ipv6 isdnlog jabber jpeg lzw lzw-tiff mp3 mpeg ncurses nls nptl nptlonly ogg opengl pam pcre pdflib png pppd pri python qt3 qt4 quicktime readline reflection sdl session smp speex spell spl ssl svg tcltk tcpd theora threads tiff truetype truetype-fonts type1-fonts unicode usb utf8 video_cards_i810 video_cards_vga vim-with-x vorbis xanim xattr xinerama xorg xpm xv xvid xvmc zaptel zlib elibc_glibc input_devices_evdev kernel_linux userland_GNU video_cards_apm video_cards_ark video_cards_ati video_cards_chips video_cards_cirrus video_cards_cyrix video_cards_dummy video_cards_fbdev video_cards_glint video_cards_i128 video_cards_mga video_cards_neomagic video_cards_nv video_cards_rendition video_cards_s3 video_cards_s3virge video_cards_savage video_cards_siliconmotion video_cards_sis video_cards_sisusb video_cards_tdfx video_cards_tga video_cards_trident video_cards_tseng video_cards_v4l video_cards_vesa video_cards_via video_cards_vmware video_cards_voodoo"
Unset:  CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LDFLAGS, LINGUAS, PORTAGE_RSYNC_EXTRA_OPTS

Hope it helps.

Thanks again,
    Alberto