------ =_NextPart_000_01BDBFAC.3BEC77F8
Content-Type: text/plain
Help! Since July 31 my Exchange Mail system has received nearly 600
error messages like the following. Apparently your system is attempting
to use my system to send and receive mail for a discussion group. I am
going to block all mail from your site to prevent incoming mail, but I
thought you might want to know that this is happening.
Ken Purcell, Technology Coordinator
Murray State University College of Education
Murray, KY 42071
(502) 762-6123
-----Original Message-----
From: COE Exchange Administrator
Sent: Sunday, August 02, 1998 10:44 AM
To: Purcell, Ken - COE Tech. Coor.
Subject: FW: Notification: Inbound Mail Failure
> ----------
> From: COE Exchange Administrator
> Sent: Sunday, August 02, 1998 10:43:45 AM
> To: COE Exchange Administrator
> Subject: Notification: Inbound Mail Failure
> Auto forwarded by a Rule
>
The following recipients did not receive the attached mail. A NDR was
not sent to the originator for the following recipients for one of the
following reasons:
* The Delivery Status Notification options did not request
failure notification, or requested no notification.
* The message was of precedence bulk.
NDR reasons are listed with each recipient, along with the notification
requested for that recipient,
or the precedence.
<linux@msmail.coe.mursuky.edu> linux@msmail.coe.mursuky.edu
MSEXCH:IMS:MSU:COE:COEEXCHANGE 0 (000C05A6) Unknown Recipient
Precedence: bulk
The message that caused this notification was:
------ =_NextPart_000_01BDBFAC.3BEC77F8
Content-Type: message/rfc822
Message-ID: <19980802172053.13597@albireo.ucw.cz>
From: Martin Mares <mj@ucw.cz>
To: Geert Uytterhoeven <Geert.Uytterhoeven@cs.kuleuven.ac.be>
Cc: Gabriel Paubert <paubert@iram.es>, Linux kernel
<linux-kernel@vger.rutgers.edu>
Subject: Re: S3 High Speed text font support in vgacon.c [patch 2.1.112]
Date: Sun, 2 Aug 1998 10:20:53 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.1960.3)
Content-Type: text/plain
Hi,
> I've been thinking about adding code for that to the kernel, but it's
not
> trivial: how do you find out which devices have been assigned PCI
resources
> already? Is this the correct way?
>
> oldaddr = pci_read(PCI_BASE_ADDRESS_i);
> pci_write(PCI_BASE_ADDRESS_i, -1);
> newaddr = pci_read(PCI_BASE_ADDRESS_i);
> if (oldaddr == newaddr) {
> /* not assigned */
> newaddr = pci_alloc(newaddr);
> pci_write(PCI_BASE_ADDRESS_i, newaddr);
> } else {
> /* assigned */
> pci_write(PCI_BASE_ADDRESS_i, oldaddr);
> }
>
> OK, this is a bit simplistic. I need two passes to prealloc the
already
> assigned stuff. I cannot reassign new adresses to already assigned
stuff since
> those adresses may be in the Open Firmware device tree properties, and
thus
> can't be changed.
You should disable PCI_COMMAND_IO and PCI_COMMAND_MEMORY before
writing
to the base address registers and enable it afterwards (but don't enable
IO
where there are no I/O ports and the same holds for enabling memory).
The real problem is that you can't write a simple pci_alloc function
since
you need to handle PCI-to-PCI bridges. You also need to do some fixup
for early
S3 cards which errorneously report 16M address space instead of 32M (see
XFree86
probing routines for an work-around).
I plan to include address allocation in the generic PCI subsystem for
2.3
(calling arch-dependent functions for address space management, but
handling
bridges and buggy devices itself), since it's needed for proper support
of
hot-pluggable devices (CardBus etc.) and we will finally get rid of the
ugly
IDE address assignment hacks, too.
Have a nice fortnight
-- Martin `MJ' Mares <mj@ucw.cz> http://atrey.karlin.mff.cuni.cz/~mj/ Faculty of Math and Physics, Charles University, Prague, Czech Rep., Earth "Lisp Users: Due to the holiday, there will be no garbage collection on Monday."- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html
------ =_NextPart_000_01BDBFAC.3BEC77F8--
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html