Hello Paul,
I understand the I/O rebasing in your patch, but I don't for the IRQ.
You can ignore the ne2k_low.s file, as it is only used in a standalone
unit test, not in ELKS kernel.
You redefined NE2K_IRQ to 2, but you did not modified the code in the
interrupt management part.
Please read https://github.com/jbruchon/elks/issues/133 for details.
For the ping, the ICMP protocol is not implemented in the KTCP module.
You should use the "arping" command instead.
Regards,
MFLD
Le 23/08/2018 à 18:43, Paul Osmialowski a écrit :
Hi Marc,
Finally I managed to reach my old flat where I keep my old XT. I did
modifications to ELKS as in the attachment and booted it from floppy
(still don't know how to boot it over XT-IDE from HD image! I managed to
buy, just for ELKS experiments, 32MB CF card in 2018 from some on-line
store in Japan! dd to /dev/sdb1 doesn't seem to copy bootstrap code to
the boot sector, dd directly to /dev/sdb creates whole of a mess in place
of partition table, and it still doesn't boot).
As I booted newly built ELKS, this time there was no interrupt acquisition
error, frankly no errors at all, brief message that ne2k driver was
initialized properly.
I tried to ping it by mac address (found some macping script on
stackoverflow: https://stackoverflow.com/a/43478858) unfortunately, no
reply (alhough the diodes on the RJ-45 socket were blinking during that).
It would be easier to have IP address set, but I couldn't find anything
like that in menuconfig. I guess more progress will be possible when I get
there next time.
Thanks,
Paul
On Thu, 12 Apr 2018, Paul Osmialowski wrote:
Hi Marc,
Thanks for the hint, it saved me a lot of effort, I'll do
further experiments with N2K driver as soon as I'll be able to run this
machine again.
Thanks,
Paul
On Thu, 12 Apr 2018, Marc-François Lucca-Daniau wrote:
Thanks for the snapshot, it helped a lot.
The main chip of your card is the WD83C690, that is a clone of the
DP8390D (same packaging with the first pin in the middle of one side).
After reading the PD8390D datasheet, I suddenly remembered that this
chip is part of the NE1K / NE2K reference design.
So, to answer your question, it would be easy to tune the existing
ELKS N2K driver for your card, without any challenge. You would have
only to tune the IRQ and the I/O base, and address the usual tricks of
the NE2K implementations. As the ROM slot is not populated, I guess
you could forget the MEM base.
MFLD
2018-04-12 17:34 GMT+02:00 Paul Osmialowski <pawelo@xxxxxxxxxxx>:
Hi Guys,
Attached is the requested snapshot. Unfortunately, some change occured in
the meantime, and now I need to postpone activities on this until summer
cos nowadays I have very limited access to the place where this stuff is
kept.
Other than that, under FreeDOS it's configured as such:
Packet driver for SMC8xxx adapters
Packet driver interrupt 0x60 (96)
Adapter: 8003WC
I/O port: 0x240 (576)
Interrupt number: 0x2 (2)
Memory address: 0xCCE00 (839168)
MAC: 00:00:c0:xx:xx:xx (so it's https://www.macvendorlookup.com/browse/192
- Western Digital)
Thanks,
Paul
On Mon, 9 Apr 2018, Marc-François Lucca-Daniau wrote:
Could you at least take one or two snapshots of your card, to be able
to see the ICs references ?
MFLD
2018-04-09 15:00 GMT+02:00 Paul Osmialowski <pawelo@xxxxxxxxxxx>:
Unfortunately, I'm afraid only Donald Becker may have in-depth knowledge
abot the interior of such a card.
On Mon, 9 Apr 2018, Marc-François Lucca-Daniau wrote:
Hello Paul,
The SMC8003WC looks like to be an ISA card, so I see no big challenge
to implement its driver in ELKS.
The problem would be to test that driver, as I got no such card, and
QEMU does not emulate this one.
Do you have the WD8003 datasheet ?
MFLD
2018-04-08 21:18 GMT+02:00 Paul Osmialowski <pawelo@xxxxxxxxxxx>:
Hello,
I've found SMC8003WC an extremly useful card as it has normal RJ-45 socket
and it can 'talk' to my modern era machines (ping and telnet them by
their IP addresses from FreeDOS). I believe that under Linux it is
operated by 1993-94's drivers/net/ethernet/8390/wd.c driver ('This is a
driver for WD8003 and WD8013 "compatible" ethercards'). What are the
possible challenges in porting such an driver from 'full' Linux to ELKS?
Best regards,
Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-8086" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-8086" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-8086" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-8086" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
