Searched hist:af4394d40ac13e07d87b5cf74bb0c20230136a70 (Results 1 – 3 of 3) sorted by relevance
| /freebsd/sys/dev/isp/ |
| H A D | ispreg.h | diff af4394d40ac13e07d87b5cf74bb0c20230136a70 Fri Feb 23 22:59:21 CET 2007 Matt Jacob <mjacob@FreeBSD.org> Don't attempt to load illegal hard loop addresses into
an ICB. This shows up on card restarts, and usually for
2200-2300 cards. What happens is that we start up,
attempting to acquire a hard address. We end up instead
being an F-port topology, which reports out a loop id
of 0xff (or 0xffff for 2K Login f/w). Then, if we restart,
we end up telling the card to go off an acquire this loop
address, which the card then rejects. Bah.
Compilation fixes from Solaris port.
diff af4394d40ac13e07d87b5cf74bb0c20230136a70 Fri Feb 23 22:59:21 CET 2007 Matt Jacob <mjacob@FreeBSD.org> Don't attempt to load illegal hard loop addresses into
an ICB. This shows up on card restarts, and usually for
2200-2300 cards. What happens is that we start up,
attempting to acquire a hard address. We end up instead
being an F-port topology, which reports out a loop id
of 0xff (or 0xffff for 2K Login f/w). Then, if we restart,
we end up telling the card to go off an acquire this loop
address, which the card then rejects. Bah.
Compilation fixes from Solaris port.
|
| H A D | ispmbox.h | diff af4394d40ac13e07d87b5cf74bb0c20230136a70 Fri Feb 23 22:59:21 CET 2007 Matt Jacob <mjacob@FreeBSD.org> Don't attempt to load illegal hard loop addresses into
an ICB. This shows up on card restarts, and usually for
2200-2300 cards. What happens is that we start up,
attempting to acquire a hard address. We end up instead
being an F-port topology, which reports out a loop id
of 0xff (or 0xffff for 2K Login f/w). Then, if we restart,
we end up telling the card to go off an acquire this loop
address, which the card then rejects. Bah.
Compilation fixes from Solaris port.
diff af4394d40ac13e07d87b5cf74bb0c20230136a70 Fri Feb 23 22:59:21 CET 2007 Matt Jacob <mjacob@FreeBSD.org> Don't attempt to load illegal hard loop addresses into
an ICB. This shows up on card restarts, and usually for
2200-2300 cards. What happens is that we start up,
attempting to acquire a hard address. We end up instead
being an F-port topology, which reports out a loop id
of 0xff (or 0xffff for 2K Login f/w). Then, if we restart,
we end up telling the card to go off an acquire this loop
address, which the card then rejects. Bah.
Compilation fixes from Solaris port.
|
| H A D | isp.c | diff af4394d40ac13e07d87b5cf74bb0c20230136a70 Fri Feb 23 22:59:21 CET 2007 Matt Jacob <mjacob@FreeBSD.org> Don't attempt to load illegal hard loop addresses into
an ICB. This shows up on card restarts, and usually for
2200-2300 cards. What happens is that we start up,
attempting to acquire a hard address. We end up instead
being an F-port topology, which reports out a loop id
of 0xff (or 0xffff for 2K Login f/w). Then, if we restart,
we end up telling the card to go off an acquire this loop
address, which the card then rejects. Bah.
Compilation fixes from Solaris port.
diff af4394d40ac13e07d87b5cf74bb0c20230136a70 Fri Feb 23 22:59:21 CET 2007 Matt Jacob <mjacob@FreeBSD.org> Don't attempt to load illegal hard loop addresses into
an ICB. This shows up on card restarts, and usually for
2200-2300 cards. What happens is that we start up,
attempting to acquire a hard address. We end up instead
being an F-port topology, which reports out a loop id
of 0xff (or 0xffff for 2K Login f/w). Then, if we restart,
we end up telling the card to go off an acquire this loop
address, which the card then rejects. Bah.
Compilation fixes from Solaris port.
|