€•Y      Œsphinx.addnodes”Œdocument”“”)”}”(Œ	rawsource”Œ ”Œchildren”]”(Œtranslations”ŒLanguagesNode”“”)”}”(hhh]”(h Œpending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ
attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ	refdomain”Œstd”Œreftype”Œdoc”Œ	reftarget”ŒE/translations/zh_CN/networking/device_drivers/ethernet/davicom/dm9000”Œmodname”NŒ	classname”NŒrefexplicit”ˆuŒtagname”hhhubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”ŒE/translations/zh_TW/networking/device_drivers/ethernet/davicom/dm9000”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”ŒE/translations/it_IT/networking/device_drivers/ethernet/davicom/dm9000”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”ŒE/translations/ja_JP/networking/device_drivers/ethernet/davicom/dm9000”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”ŒE/translations/ko_KR/networking/device_drivers/ethernet/davicom/dm9000”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒPortuguese (Brazilian)”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”ŒE/translations/pt_BR/networking/device_drivers/ethernet/davicom/dm9000”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒSpanish”…””}”hh–sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”ŒE/translations/sp_SP/networking/device_drivers/ethernet/davicom/dm9000”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h
hhŒ	_document”hŒsource”NŒline”NubhŒcomment”“”)”}”(hŒ SPDX-License-Identifier: GPL-2.0”h]”hŒ SPDX-License-Identifier: GPL-2.0”…””}”hh·sbah}”(h]”h ]”h"]”h$]”h&]”Œ	xml:space”Œpreserve”uh1hµhhh²hh³Œ_/var/lib/git/docbuild/linux/Documentation/networking/device_drivers/ethernet/davicom/dm9000.rst”h´KubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒDM9000 Network driver”h]”hŒDM9000 Network driver”…””}”(hhÏh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhhÊh²hh³hÇh´KubhŒ	paragraph”“”)”}”(hŒ"Copyright 2008 Simtec Electronics,”h]”hŒ"Copyright 2008 Simtec Electronics,”…””}”(hhßh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KhhÊh²hubhŒblock_quote”“”)”}”(hŒ4Ben Dooks <ben@simtec.co.uk> <ben-linux@fluff.org>

”h]”hÞ)”}”(hŒ2Ben Dooks <ben@simtec.co.uk> <ben-linux@fluff.org>”h]”(hŒBen Dooks <”…””}”(hhóh²hh³Nh´NubhŒ	reference”“”)”}”(hŒben@simtec.co.uk”h]”hŒben@simtec.co.uk”…””}”(hhýh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œmailto:ben@simtec.co.uk”uh1hûhhóubhŒ> <”…””}”(hhóh²hh³Nh´Nubhü)”}”(hŒben-linux@fluff.org”h]”hŒben-linux@fluff.org”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œmailto:ben-linux@fluff.org”uh1hûhhóubhŒ>”…””}”(hhóh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K	hhïubah}”(h]”h ]”h"]”h$]”h&]”uh1híh³hÇh´K	hhÊh²hubhÉ)”}”(hhh]”(hÎ)”}”(hŒIntroduction”h]”hŒIntroduction”…””}”(hj4  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj1  h²hh³hÇh´KubhÞ)”}”(hŒœThis file describes how to use the DM9000 platform-device based network driver
that is contained in the files drivers/net/dm9000.c and drivers/net/dm9000.h.”h]”hŒœThis file describes how to use the DM9000 platform-device based network driver
that is contained in the files drivers/net/dm9000.c and drivers/net/dm9000.h.”…””}”(hjB  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Khj1  h²hubhÞ)”}”(hŒðThe driver supports three DM9000 variants, the DM9000E which is the first chip
supported as well as the newer DM9000A and DM9000B devices. It is currently
maintained and tested by Ben Dooks, who should be CC: to any patches for this
driver.”h]”hŒðThe driver supports three DM9000 variants, the DM9000E which is the first chip
supported as well as the newer DM9000A and DM9000B devices. It is currently
maintained and tested by Ben Dooks, who should be CC: to any patches for this
driver.”…””}”(hjP  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Khj1  h²hubeh}”(h]”Œintroduction”ah ]”h"]”Œintroduction”ah$]”h&]”uh1hÈhhÊh²hh³hÇh´KubhÉ)”}”(hhh]”(hÎ)”}”(hŒDefining the platform device”h]”hŒDefining the platform device”…””}”(hji  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjf  h²hh³hÇh´KubhÞ)”}”(hŒLThe minimum set of resources attached to the platform device are as follows:”h]”hŒLThe minimum set of resources attached to the platform device are as follows:”…””}”(hjw  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Khjf  h²hubhî)”}”(hŒ™1) The physical address of the address register
2) The physical address of the data register
3) The IRQ line the device's interrupt pin is connected to.
”h]”hŒenumerated_list”“”)”}”(hhh]”(hŒ	list_item”“”)”}”(hŒ,The physical address of the address register”h]”hÞ)”}”(hj’  h]”hŒ,The physical address of the address register”…””}”(hj”  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Khj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jŽ  hj‹  ubj  )”}”(hŒ)The physical address of the data register”h]”hÞ)”}”(hj©  h]”hŒ)The physical address of the data register”…””}”(hj«  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Khj§  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jŽ  hj‹  ubj  )”}”(hŒ9The IRQ line the device's interrupt pin is connected to.
”h]”hÞ)”}”(hŒ8The IRQ line the device's interrupt pin is connected to.”h]”hŒ:The IRQ line the deviceâ€™s interrupt pin is connected to.”…””}”(hjÂ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Khj¾  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jŽ  hj‹  ubeh}”(h]”h ]”h"]”h$]”h&]”Œenumtype”Œarabic”Œprefix”hŒsuffix”Œ)”uh1j‰  hj…  ubah}”(h]”h ]”h"]”h$]”h&]”uh1híh³hÇh´Khjf  h²hubhÞ)”}”(hŒ¢These resources should be specified in that order, as the ordering of the
two address regions is important (the driver expects these to be address
and then data).”h]”hŒ¢These resources should be specified in that order, as the ordering of the
two address regions is important (the driver expects these to be address
and then data).”…””}”(hjç  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K!hjf  h²hubhÞ)”}”(hŒ2An example from arch/arm/mach-s3c/mach-bast.c is::”h]”hŒ1An example from arch/arm/mach-s3c/mach-bast.c is:”…””}”(hjõ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K%hjf  h²hubhŒliteral_block”“”)”}”(hX  static struct resource bast_dm9k_resource[] = {
      [0] = {
              .start = S3C2410_CS5 + BAST_PA_DM9000,
              .end   = S3C2410_CS5 + BAST_PA_DM9000 + 3,
              .flags = IORESOURCE_MEM,
      },
      [1] = {
              .start = S3C2410_CS5 + BAST_PA_DM9000 + 0x40,
              .end   = S3C2410_CS5 + BAST_PA_DM9000 + 0x40 + 0x3f,
              .flags = IORESOURCE_MEM,
      },
      [2] = {
              .start = IRQ_DM9000,
              .end   = IRQ_DM9000,
              .flags = IORESOURCE_IRQ | IORESOURCE_IRQ_HIGHLEVEL,
      }
};

static struct platform_device bast_device_dm9k = {
      .name           = "dm9000",
      .id             = 0,
      .num_resources  = ARRAY_SIZE(bast_dm9k_resource),
      .resource       = bast_dm9k_resource,
};”h]”hX  static struct resource bast_dm9k_resource[] = {
      [0] = {
              .start = S3C2410_CS5 + BAST_PA_DM9000,
              .end   = S3C2410_CS5 + BAST_PA_DM9000 + 3,
              .flags = IORESOURCE_MEM,
      },
      [1] = {
              .start = S3C2410_CS5 + BAST_PA_DM9000 + 0x40,
              .end   = S3C2410_CS5 + BAST_PA_DM9000 + 0x40 + 0x3f,
              .flags = IORESOURCE_MEM,
      },
      [2] = {
              .start = IRQ_DM9000,
              .end   = IRQ_DM9000,
              .flags = IORESOURCE_IRQ | IORESOURCE_IRQ_HIGHLEVEL,
      }
};

static struct platform_device bast_device_dm9k = {
      .name           = "dm9000",
      .id             = 0,
      .num_resources  = ARRAY_SIZE(bast_dm9k_resource),
      .resource       = bast_dm9k_resource,
};”…””}”hj  sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j  h³hÇh´K'hjf  h²hubhÞ)”}”(hX  Note the setting of the IRQ trigger flag in bast_dm9k_resource[2].flags,
as this will generate a warning if it is not present. The trigger from
the flags field will be passed to request_irq() when registering the IRQ
handler to ensure that the IRQ is setup correctly.”h]”hX  Note the setting of the IRQ trigger flag in bast_dm9k_resource[2].flags,
as this will generate a warning if it is not present. The trigger from
the flags field will be passed to request_irq() when registering the IRQ
handler to ensure that the IRQ is setup correctly.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K@hjf  h²hubhÞ)”}”(hŒÑThis shows a typical platform device, without the optional configuration
platform data supplied. The next example uses the same resources, but adds
the optional platform data to pass extra configuration data::”h]”hŒÐThis shows a typical platform device, without the optional configuration
platform data supplied. The next example uses the same resources, but adds
the optional platform data to pass extra configuration data:”…””}”(hj!  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KEhjf  h²hubj  )”}”(hX–  static struct dm9000_plat_data bast_dm9k_platdata = {
      .flags          = DM9000_PLATF_16BITONLY,
};

static struct platform_device bast_device_dm9k = {
      .name           = "dm9000",
      .id             = 0,
      .num_resources  = ARRAY_SIZE(bast_dm9k_resource),
      .resource       = bast_dm9k_resource,
      .dev            = {
              .platform_data = &bast_dm9k_platdata,
      }
};”h]”hX–  static struct dm9000_plat_data bast_dm9k_platdata = {
      .flags          = DM9000_PLATF_16BITONLY,
};

static struct platform_device bast_device_dm9k = {
      .name           = "dm9000",
      .id             = 0,
      .num_resources  = ARRAY_SIZE(bast_dm9k_resource),
      .resource       = bast_dm9k_resource,
      .dev            = {
              .platform_data = &bast_dm9k_platdata,
      }
};”…””}”hj/  sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆuh1j  h³hÇh´KIhjf  h²hubhÞ)”}”(hŒKThe platform data is defined in include/linux/dm9000.h and described below.”h]”hŒKThe platform data is defined in include/linux/dm9000.h and described below.”…””}”(hj=  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KWhjf  h²hubeh}”(h]”Œdefining-the-platform-device”ah ]”h"]”Œdefining the platform device”ah$]”h&]”uh1hÈhhÊh²hh³hÇh´KubhÉ)”}”(hhh]”(hÎ)”}”(hŒPlatform data”h]”hŒPlatform data”…””}”(hjV  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjS  h²hh³hÇh´K[ubhÞ)”}”(hŒÂExtra platform data for the DM9000 can describe the IO bus width to the
device, whether or not an external PHY is attached to the device and
the availability of an external configuration EEPROM.”h]”hŒÂExtra platform data for the DM9000 can describe the IO bus width to the
device, whether or not an external PHY is attached to the device and
the availability of an external configuration EEPROM.”…””}”(hjd  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K]hjS  h²hubhÞ)”}”(hŒ<The flags for the platform data .flags field are as follows:”h]”hŒ<The flags for the platform data .flags field are as follows:”…””}”(hjr  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KahjS  h²hubhÞ)”}”(hŒDM9000_PLATF_8BITONLY”h]”hŒDM9000_PLATF_8BITONLY”…””}”(hj€  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KchjS  h²hubhî)”}”(hŒ,The IO should be done with 8bit operations.
”h]”hÞ)”}”(hŒ+The IO should be done with 8bit operations.”h]”hŒ+The IO should be done with 8bit operations.”…””}”(hj’  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KehjŽ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1híh³hÇh´KehjS  h²hubhÞ)”}”(hŒDM9000_PLATF_16BITONLY”h]”hŒDM9000_PLATF_16BITONLY”…””}”(hj¦  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KghjS  h²hubhî)”}”(hŒ-The IO should be done with 16bit operations.
”h]”hÞ)”}”(hŒ,The IO should be done with 16bit operations.”h]”hŒ,The IO should be done with 16bit operations.”…””}”(hj¸  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Kihj´  ubah}”(h]”h ]”h"]”h$]”h&]”uh1híh³hÇh´KihjS  h²hubhÞ)”}”(hŒDM9000_PLATF_32BITONLY”h]”hŒDM9000_PLATF_32BITONLY”…””}”(hjÌ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KkhjS  h²hubhî)”}”(hŒ-The IO should be done with 32bit operations.
”h]”hÞ)”}”(hŒ,The IO should be done with 32bit operations.”h]”hŒ,The IO should be done with 32bit operations.”…””}”(hjÞ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KmhjÚ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1híh³hÇh´KmhjS  h²hubhÞ)”}”(hŒDM9000_PLATF_EXT_PHY”h]”hŒDM9000_PLATF_EXT_PHY”…””}”(hjò  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KohjS  h²hubhî)”}”(hŒ*The chip is connected to an external PHY.
”h]”hÞ)”}”(hŒ)The chip is connected to an external PHY.”h]”hŒ)The chip is connected to an external PHY.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Kqhj   ubah}”(h]”h ]”h"]”h$]”h&]”uh1híh³hÇh´KqhjS  h²hubhÞ)”}”(hŒDM9000_PLATF_NO_EEPROM”h]”hŒDM9000_PLATF_NO_EEPROM”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KshjS  h²hubhî)”}”(hŒwThis can be used to signify that the board does not have an
EEPROM, or that the EEPROM should be hidden from the user.
”h]”hÞ)”}”(hŒvThis can be used to signify that the board does not have an
EEPROM, or that the EEPROM should be hidden from the user.”h]”hŒvThis can be used to signify that the board does not have an
EEPROM, or that the EEPROM should be hidden from the user.”…””}”(hj*  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Kuhj&  ubah}”(h]”h ]”h"]”h$]”h&]”uh1híh³hÇh´KuhjS  h²hubhÞ)”}”(hŒDM9000_PLATF_SIMPLE_PHY”h]”hŒDM9000_PLATF_SIMPLE_PHY”…””}”(hj>  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KxhjS  h²hubhî)”}”(hXm  Switch to using the simpler PHY polling method which does not
try and read the MII PHY state regularly. This is only available
when using the internal PHY. See the section on link state polling
for more information.

The config symbol DM9000_FORCE_SIMPLE_PHY_POLL, Kconfig entry
"Force simple NSR based PHY polling" allows this flag to be
forced on at build time.

”h]”(hÞ)”}”(hŒ×Switch to using the simpler PHY polling method which does not
try and read the MII PHY state regularly. This is only available
when using the internal PHY. See the section on link state polling
for more information.”h]”hŒ×Switch to using the simpler PHY polling method which does not
try and read the MII PHY state regularly. This is only available
when using the internal PHY. See the section on link state polling
for more information.”…””}”(hjP  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KzhjL  ubhÞ)”}”(hŒ’The config symbol DM9000_FORCE_SIMPLE_PHY_POLL, Kconfig entry
"Force simple NSR based PHY polling" allows this flag to be
forced on at build time.”h]”hŒ–The config symbol DM9000_FORCE_SIMPLE_PHY_POLL, Kconfig entry
â€œForce simple NSR based PHY pollingâ€ allows this flag to be
forced on at build time.”…””}”(hj^  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KhjL  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1híh³hÇh´KzhjS  h²hubeh}”(h]”Œplatform-data”ah ]”h"]”Œplatform data”ah$]”h&]”uh1hÈhhÊh²hh³hÇh´K[ubhÉ)”}”(hhh]”(hÎ)”}”(hŒPHY Link state polling”h]”hŒPHY Link state polling”…””}”(hj}  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjz  h²hh³hÇh´K…ubhÞ)”}”(hŒÐThe driver keeps track of the link state and informs the network core
about link (carrier) availability. This is managed by several methods
depending on the version of the chip and on which PHY is being used.”h]”hŒÐThe driver keeps track of the link state and informs the network core
about link (carrier) availability. This is managed by several methods
depending on the version of the chip and on which PHY is being used.”…””}”(hj‹  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K‡hjz  h²hubhÞ)”}”(hŒÜFor the internal PHY, the original (and currently default) method is
to read the MII state, either when the status changes if we have the
necessary interrupt support in the chip or every two seconds via a
periodic timer.”h]”hŒÜFor the internal PHY, the original (and currently default) method is
to read the MII state, either when the status changes if we have the
necessary interrupt support in the chip or every two seconds via a
periodic timer.”…””}”(hj™  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K‹hjz  h²hubhÞ)”}”(hX)  To reduce the overhead for the internal PHY, there is now the option
of using the DM9000_FORCE_SIMPLE_PHY_POLL config, or DM9000_PLATF_SIMPLE_PHY
platform data option to read the summary information without the
expensive MII accesses. This method is faster, but does not print
as much information.”h]”hX)  To reduce the overhead for the internal PHY, there is now the option
of using the DM9000_FORCE_SIMPLE_PHY_POLL config, or DM9000_PLATF_SIMPLE_PHY
platform data option to read the summary information without the
expensive MII accesses. This method is faster, but does not print
as much information.”…””}”(hj§  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Khjz  h²hubhÞ)”}”(hŒWhen using an external PHY, the driver currently has to poll the MII
link status as there is no method for getting an interrupt on link change.”h]”hŒWhen using an external PHY, the driver currently has to poll the MII
link status as there is no method for getting an interrupt on link change.”…””}”(hjµ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K–hjz  h²hubeh}”(h]”Œphy-link-state-polling”ah ]”h"]”Œphy link state polling”ah$]”h&]”uh1hÈhhÊh²hh³hÇh´K…ubhÉ)”}”(hhh]”(hÎ)”}”(hŒDM9000A / DM9000B”h]”hŒDM9000A / DM9000B”…””}”(hjÎ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjË  h²hh³hÇh´K›ubhÞ)”}”(hŒrThese chips are functionally similar to the DM9000E and are supported easily
by the same driver. The features are:”h]”hŒrThese chips are functionally similar to the DM9000E and are supported easily
by the same driver. The features are:”…””}”(hjÜ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KhjË  h²hubhî)”}”(hŒõ1) Interrupt on internal PHY state change. This means that the periodic
   polling of the PHY status may be disabled on these devices when using
   the internal PHY.

2) TCP/UDP checksum offloading, which the driver does not currently support.

”h]”jŠ  )”}”(hhh]”(j  )”}”(hŒInterrupt on internal PHY state change. This means that the periodic
polling of the PHY status may be disabled on these devices when using
the internal PHY.
”h]”hÞ)”}”(hŒœInterrupt on internal PHY state change. This means that the periodic
polling of the PHY status may be disabled on these devices when using
the internal PHY.”h]”hŒœInterrupt on internal PHY state change. This means that the periodic
polling of the PHY status may be disabled on these devices when using
the internal PHY.”…””}”(hjõ  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K hjñ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jŽ  hjî  ubj  )”}”(hŒKTCP/UDP checksum offloading, which the driver does not currently support.

”h]”hÞ)”}”(hŒITCP/UDP checksum offloading, which the driver does not currently support.”h]”hŒITCP/UDP checksum offloading, which the driver does not currently support.”…””}”(hj  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K¤hj	  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jŽ  hjî  ubeh}”(h]”h ]”h"]”h$]”h&]”jÜ  jÝ  jÞ  hjß  jà  uh1j‰  hjê  ubah}”(h]”h ]”h"]”h$]”h&]”uh1híh³hÇh´K hjË  h²hubeh}”(h]”Œdm9000a-dm9000b”ah ]”h"]”Œdm9000a / dm9000b”ah$]”h&]”uh1hÈhhÊh²hh³hÇh´K›ubhÉ)”}”(hhh]”(hÎ)”}”(hŒethtool”h]”hŒethtool”…””}”(hj8  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj5  h²hh³hÇh´K¨ubhÞ)”}”(hŒsThe driver supports the ethtool interface for access to the driver
state information, the PHY state and the EEPROM.”h]”hŒsThe driver supports the ethtool interface for access to the driver
state information, the PHY state and the EEPROM.”…””}”(hjF  h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Kªhj5  h²hubeh}”(h]”Œethtool”ah ]”h"]”Œethtool”ah$]”h&]”uh1hÈhhÊh²hh³hÇh´K¨ubeh}”(h]”Œdm9000-network-driver”ah ]”h"]”Œdm9000 network driver”ah$]”h&]”uh1hÈhhh²hh³hÇh´Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”hÇuh1hŒcurrent_source”NŒcurrent_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(hÍNŒ	generator”NŒ	datestamp”NŒsource_link”NŒ
source_url”NŒtoc_backlinks”Œentry”Œfootnote_backlinks”KŒsectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒstrip_classes”NŒreport_level”KŒ
halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ	traceback”ˆŒinput_encoding”Œ	utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”j‡  Œerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œlanguage_code”Œen”Œrecord_dependencies”NŒconfig”NŒ	id_prefix”hŒauto_id_prefix”Œid”Œdump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”hÇŒ_destination”NŒ_config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒraw_enabled”KŒline_length_limit”M'Œpep_references”NŒpep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒrfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ	tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œsmart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œdocinfo_xform”KŒsectsubtitle_xform”‰Œimage_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”Œnameids”}”(ja  j^  jc  j`  jP  jM  jw  jt  jÈ  jÅ  j2  j/  jY  jV  uŒ	nametypes”}”(ja  ‰jc  ‰jP  ‰jw  ‰jÈ  ‰j2  ‰jY  ‰uh}”(j^  hÊj`  j1  jM  jf  jt  jS  jÅ  jz  j/  jË  jV  j5  uŒfootnote_refs”}”Œcitation_refs”}”Œautofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ	footnotes”]”Œ	citations”]”Œautofootnote_start”KŒsymbol_footnote_start”K Œ
id_counter”Œcollections”ŒCounter”“”}”…”R”Œparse_messages”]”Œtransform_messages”]”Œtransformer”NŒinclude_log”]”Œ
decoration”Nh²hub.