Searched hist:"932 ef5b5cdfd11055e5a1239cabde17748174f78" (Results 1 – 5 of 5) sorted by relevance
| /freebsd/sys/modules/snp/ |
| H A D | Makefile | diff 932ef5b5cdfd11055e5a1239cabde17748174f78 Wed Nov 05 16:04:03 CET 2008 Ed Schouten <ed@FreeBSD.org> Reintroduce the snp(4) driver.
Because the TTY hooks interface was not finished when I imported the
MPSAFE TTY layer, I had to disconnect the snp(4) driver. This snp(4)
implementation has been sitting in my P4 branch for some time now.
Unfortunately it still doesn't use the same error handling as snp(4)
(returning codes through FIONREAD), but it should already be usable.
I'm committing this to SVN, hoping someone else could polish off its
rough edges. It's always better than having a broken driver sitting in
the tree.
diff 932ef5b5cdfd11055e5a1239cabde17748174f78 Wed Nov 05 16:04:03 CET 2008 Ed Schouten <ed@FreeBSD.org> Reintroduce the snp(4) driver.
Because the TTY hooks interface was not finished when I imported the
MPSAFE TTY layer, I had to disconnect the snp(4) driver. This snp(4)
implementation has been sitting in my P4 branch for some time now.
Unfortunately it still doesn't use the same error handling as snp(4)
(returning codes through FIONREAD), but it should already be usable.
I'm committing this to SVN, hoping someone else could polish off its
rough edges. It's always better than having a broken driver sitting in
the tree.
|
| /freebsd/share/man/man4/ |
| H A D | snp.4 | diff 932ef5b5cdfd11055e5a1239cabde17748174f78 Wed Nov 05 16:04:03 CET 2008 Ed Schouten <ed@FreeBSD.org> Reintroduce the snp(4) driver.
Because the TTY hooks interface was not finished when I imported the
MPSAFE TTY layer, I had to disconnect the snp(4) driver. This snp(4)
implementation has been sitting in my P4 branch for some time now.
Unfortunately it still doesn't use the same error handling as snp(4)
(returning codes through FIONREAD), but it should already be usable.
I'm committing this to SVN, hoping someone else could polish off its
rough edges. It's always better than having a broken driver sitting in
the tree.
diff 932ef5b5cdfd11055e5a1239cabde17748174f78 Wed Nov 05 16:04:03 CET 2008 Ed Schouten <ed@FreeBSD.org> Reintroduce the snp(4) driver.
Because the TTY hooks interface was not finished when I imported the
MPSAFE TTY layer, I had to disconnect the snp(4) driver. This snp(4)
implementation has been sitting in my P4 branch for some time now.
Unfortunately it still doesn't use the same error handling as snp(4)
(returning codes through FIONREAD), but it should already be usable.
I'm committing this to SVN, hoping someone else could polish off its
rough edges. It's always better than having a broken driver sitting in
the tree.
|
| /freebsd/sys/dev/snp/ |
| H A D | snp.c | diff 932ef5b5cdfd11055e5a1239cabde17748174f78 Wed Nov 05 16:04:03 CET 2008 Ed Schouten <ed@FreeBSD.org> Reintroduce the snp(4) driver.
Because the TTY hooks interface was not finished when I imported the
MPSAFE TTY layer, I had to disconnect the snp(4) driver. This snp(4)
implementation has been sitting in my P4 branch for some time now.
Unfortunately it still doesn't use the same error handling as snp(4)
(returning codes through FIONREAD), but it should already be usable.
I'm committing this to SVN, hoping someone else could polish off its
rough edges. It's always better than having a broken driver sitting in
the tree.
diff 932ef5b5cdfd11055e5a1239cabde17748174f78 Wed Nov 05 16:04:03 CET 2008 Ed Schouten <ed@FreeBSD.org> Reintroduce the snp(4) driver.
Because the TTY hooks interface was not finished when I imported the
MPSAFE TTY layer, I had to disconnect the snp(4) driver. This snp(4)
implementation has been sitting in my P4 branch for some time now.
Unfortunately it still doesn't use the same error handling as snp(4)
(returning codes through FIONREAD), but it should already be usable.
I'm committing this to SVN, hoping someone else could polish off its
rough edges. It's always better than having a broken driver sitting in
the tree.
|
| /freebsd/sys/modules/ |
| H A D | Makefile | diff 932ef5b5cdfd11055e5a1239cabde17748174f78 Wed Nov 05 16:04:03 CET 2008 Ed Schouten <ed@FreeBSD.org> Reintroduce the snp(4) driver.
Because the TTY hooks interface was not finished when I imported the
MPSAFE TTY layer, I had to disconnect the snp(4) driver. This snp(4)
implementation has been sitting in my P4 branch for some time now.
Unfortunately it still doesn't use the same error handling as snp(4)
(returning codes through FIONREAD), but it should already be usable.
I'm committing this to SVN, hoping someone else could polish off its
rough edges. It's always better than having a broken driver sitting in
the tree.
diff 932ef5b5cdfd11055e5a1239cabde17748174f78 Wed Nov 05 16:04:03 CET 2008 Ed Schouten <ed@FreeBSD.org> Reintroduce the snp(4) driver.
Because the TTY hooks interface was not finished when I imported the
MPSAFE TTY layer, I had to disconnect the snp(4) driver. This snp(4)
implementation has been sitting in my P4 branch for some time now.
Unfortunately it still doesn't use the same error handling as snp(4)
(returning codes through FIONREAD), but it should already be usable.
I'm committing this to SVN, hoping someone else could polish off its
rough edges. It's always better than having a broken driver sitting in
the tree.
|
| /freebsd/sys/conf/ |
| H A D | NOTES | diff 932ef5b5cdfd11055e5a1239cabde17748174f78 Wed Nov 05 16:04:03 CET 2008 Ed Schouten <ed@FreeBSD.org> Reintroduce the snp(4) driver.
Because the TTY hooks interface was not finished when I imported the
MPSAFE TTY layer, I had to disconnect the snp(4) driver. This snp(4)
implementation has been sitting in my P4 branch for some time now.
Unfortunately it still doesn't use the same error handling as snp(4)
(returning codes through FIONREAD), but it should already be usable.
I'm committing this to SVN, hoping someone else could polish off its
rough edges. It's always better than having a broken driver sitting in
the tree.
diff 932ef5b5cdfd11055e5a1239cabde17748174f78 Wed Nov 05 16:04:03 CET 2008 Ed Schouten <ed@FreeBSD.org> Reintroduce the snp(4) driver.
Because the TTY hooks interface was not finished when I imported the
MPSAFE TTY layer, I had to disconnect the snp(4) driver. This snp(4)
implementation has been sitting in my P4 branch for some time now.
Unfortunately it still doesn't use the same error handling as snp(4)
(returning codes through FIONREAD), but it should already be usable.
I'm committing this to SVN, hoping someone else could polish off its
rough edges. It's always better than having a broken driver sitting in
the tree.
|