Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1646760 > unrolled thread
| Started by | Jan Kiszka <jan.kiszka@siemens.com> |
|---|---|
| First post | 2017-05-22 13:20 +0200 |
| Last post | 2017-05-22 20:30 +0200 |
| Articles | 4 — 2 participants |
Back to article view | Back to linux.kernel
[PATCH 0/3] stmmac: pci: Refactor DMI probing Jan Kiszka <jan.kiszka@siemens.com> - 2017-05-22 13:20 +0200
Re: [PATCH 0/3] stmmac: pci: Refactor DMI probing David Miller <davem@davemloft.net> - 2017-05-22 18:40 +0200
Re: [PATCH 0/3] stmmac: pci: Refactor DMI probing Jan Kiszka <jan.kiszka@siemens.com> - 2017-05-22 19:10 +0200
Re: [PATCH 0/3] stmmac: pci: Refactor DMI probing David Miller <davem@davemloft.net> - 2017-05-22 20:30 +0200
| From | Jan Kiszka <jan.kiszka@siemens.com> |
|---|---|
| Date | 2017-05-22 13:20 +0200 |
| Subject | [PATCH 0/3] stmmac: pci: Refactor DMI probing |
| Message-ID | <tJTxw-50U-13@gated-at.bofh.it> |
Some cleanups of the way we probe DMI platforms in the driver. Reduces a bit of open-coding and makes the logic easier reusable for any potential DMI platform != Quark. Tested on IOT2000 and Galileo Gen2. Jan Jan Kiszka (3): stmmac: pci: Overcome stmmac_pci_info structure stmmac: pci: Make stmmac_pci_find_phy_addr truly generic stmmac: pci: Use dmi_system_id table for retrieving PHY addresses drivers/net/ethernet/stmicro/stmmac/stmmac_pci.c | 184 ++++++++++++----------- 1 file changed, 99 insertions(+), 85 deletions(-) -- 2.12.0
[toc] | [next] | [standalone]
| From | David Miller <davem@davemloft.net> |
|---|---|
| Date | 2017-05-22 18:40 +0200 |
| Message-ID | <tJYxc-83k-25@gated-at.bofh.it> |
| In reply to | #1646760 |
From: Jan Kiszka <jan.kiszka@siemens.com> Date: Mon, 22 May 2017 13:12:06 +0200 > Some cleanups of the way we probe DMI platforms in the driver. Reduces > a bit of open-coding and makes the logic easier reusable for any > potential DMI platform != Quark. > > Tested on IOT2000 and Galileo Gen2. This doesn't compile: drivers/net/ethernet/stmicro/stmmac/stmmac_pci.c:285:3: error: initializer element is not computable at load time (kernel_ulong_t)&stmmac_default_setup, ^ drivers/net/ethernet/stmicro/stmmac/stmmac_pci.c:285:3: note: (near initialization for ‘stmmac_id_table[0].class’) drivers/net/ethernet/stmicro/stmmac/stmmac_pci.c:289:3: error: initializer element is not computable at load time (kernel_ulong_t)&stmmac_default_setup, ^ drivers/net/ethernet/stmicro/stmmac/stmmac_pci.c:289:3: note: (near initialization for ‘stmmac_id_table[1].class’) scripts/Makefile.build:302: recipe for target 'drivers/net/ethernet/stmicro/stmmac/stmmac_pci.o' failed make[5]: *** [drivers/net/ethernet/stmicro/stmmac/stmmac_pci.o] Error 1
[toc] | [prev] | [next] | [standalone]
| From | Jan Kiszka <jan.kiszka@siemens.com> |
|---|---|
| Date | 2017-05-22 19:10 +0200 |
| Message-ID | <tJZ0e-8sT-31@gated-at.bofh.it> |
| In reply to | #1647138 |
On 2017-05-22 18:35, David Miller wrote: > From: Jan Kiszka <jan.kiszka@siemens.com> > Date: Mon, 22 May 2017 13:12:06 +0200 > >> Some cleanups of the way we probe DMI platforms in the driver. Reduces >> a bit of open-coding and makes the logic easier reusable for any >> potential DMI platform != Quark. >> >> Tested on IOT2000 and Galileo Gen2. > > This doesn't compile: > > drivers/net/ethernet/stmicro/stmmac/stmmac_pci.c:285:3: error: initializer element is not computable at load time > (kernel_ulong_t)&stmmac_default_setup, > ^ > drivers/net/ethernet/stmicro/stmmac/stmmac_pci.c:285:3: note: (near initialization for ‘stmmac_id_table[0].class’) > drivers/net/ethernet/stmicro/stmmac/stmmac_pci.c:289:3: error: initializer element is not computable at load time > (kernel_ulong_t)&stmmac_default_setup, > ^ > drivers/net/ethernet/stmicro/stmmac/stmmac_pci.c:289:3: note: (near initialization for ‘stmmac_id_table[1].class’) > scripts/Makefile.build:302: recipe for target 'drivers/net/ethernet/stmicro/stmmac/stmmac_pci.o' failed > make[5]: *** [drivers/net/ethernet/stmicro/stmmac/stmmac_pci.o] Error 1 > Hmm. Which arch is this? Jan
[toc] | [prev] | [next] | [standalone]
| From | David Miller <davem@davemloft.net> |
|---|---|
| Date | 2017-05-22 20:30 +0200 |
| Message-ID | <tK0fD-HF-5@gated-at.bofh.it> |
| In reply to | #1647198 |
From: Jan Kiszka <jan.kiszka@siemens.com> Date: Mon, 22 May 2017 19:06:07 +0200 > On 2017-05-22 18:35, David Miller wrote: >> From: Jan Kiszka <jan.kiszka@siemens.com> >> Date: Mon, 22 May 2017 13:12:06 +0200 >> >>> Some cleanups of the way we probe DMI platforms in the driver. Reduces >>> a bit of open-coding and makes the logic easier reusable for any >>> potential DMI platform != Quark. >>> >>> Tested on IOT2000 and Galileo Gen2. >> >> This doesn't compile: >> >> drivers/net/ethernet/stmicro/stmmac/stmmac_pci.c:285:3: error: initializer element is not computable at load time >> (kernel_ulong_t)&stmmac_default_setup, >> ^ >> drivers/net/ethernet/stmicro/stmmac/stmmac_pci.c:285:3: note: (near initialization for ‘stmmac_id_table[0].class’) >> drivers/net/ethernet/stmicro/stmmac/stmmac_pci.c:289:3: error: initializer element is not computable at load time >> (kernel_ulong_t)&stmmac_default_setup, >> ^ >> drivers/net/ethernet/stmicro/stmmac/stmmac_pci.c:289:3: note: (near initialization for ‘stmmac_id_table[1].class’) >> scripts/Makefile.build:302: recipe for target 'drivers/net/ethernet/stmicro/stmmac/stmmac_pci.o' failed >> make[5]: *** [drivers/net/ethernet/stmicro/stmmac/stmmac_pci.o] Error 1 >> > > Hmm. Which arch is this? x86_64, allmodconfig
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web