| 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: Fri, 25 Jan 2008 00:38:39 +0100 From: Jiri Slaby <jirislaby@...il.com> To: Oyvind Aabling <Oyvind.Aabling@...-c.dk> CC: linux-kernel@...r.kernel.org Subject: Re: [PATCH] drivers/char/moxa.c, kernel 2.6.23.14 On 01/25/2008 12:34 AM, Oyvind Aabling wrote: > Ah, I see, you want to get rid of moxaload altogether ... Yes, I don't like such a loaders :). > I'll test your patch series as soon as I get a chance - need to put a > MOXA card into a non-production machine first, so it'll be a few days. Ok, thanks, no problem. > We have a few MOXA Intellio C320 Turbo PCI > cards, here's lspci -vvxxx for one of them: > > 02:02.0 Serial controller: Moxa Technologies Co Ltd Intellio C320 Turbo > PCI (rev 02) (prog-if 80) > Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- > ParErr- Stepping- SERR- FastB2B- > Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- > <TAbort- <MAbort- >SERR- <PERR- > Interrupt: pin A routed to IRQ 16 > Region 1: I/O ports at 9400 [size=128] > Region 2: Memory at fb200000 (32-bit, non-prefetchable) [size=16K] [...] > The other cards looks identical, except for unimportant differences > in region mapping and IRQ allocation due to system differences. OK, doesn't matter, I was just curious if region 2 is really mem space. thanks, --js -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists