lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 11 Mar 2009 06:23:36 -0700 (PDT) From: David Miller <davem@...emloft.net> To: wd@...x.de Cc: shemminger@...tta.com, yanok@...raft.com, linux-arm-kernel@...ts.arm.linux.org.uk, netdev@...r.kernel.org, dzu@...x.de Subject: Re: [PATCH] dnet: Dave DNET ethernet controller driver From: Wolfgang Denk <wd@...x.de> Date: Wed, 11 Mar 2009 10:09:38 +0100 > How do you then handle situations where this is impossible? Say, when > the firmware cannot write to those registers for example because the > ethernet controller is not even powered on (to reduce power consump- > tion), but will get powered on only in Linux when the driver gets > loaded (i. e. on demand only, not always)? That's what NVRAM, CMOS, EEPROM's and other writable long-term storage areas are for. To be quite honest with you, any ethernet device that doesn't have an EEPROM where the chip instance's ethernet address is stored is completely broken. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists