| On the other hand, there are numerous new features (GEOM, TrustedBSD,
| OpenPAM, Snapshots + background fsck, etc) being implemented in 5.x that
It appears that most of these are features that are 'use as needed.' In
other words, if I don't need them, I don't need to know about them. On
the
On Fri, Jun 07, 2002 at 02:44:27PM +0200, Poul-Henning Kamp wrote:
| In message [EMAIL PROTECTED], j mckitrick writes:
| | On the other hand, there are numerous new features (GEOM, TrustedBSD,
| | OpenPAM, Snapshots + background fsck, etc) being implemented in 5.x that
|
|
| Other than devfs
| almost all of the kernel. However, the SMP work is still in progress and
| it will get better as time goes on. One thing to note is that in 4.x,
Well, I'm trying to decide if I should make the leap to 5.0 when it
comes out (my early adopter side talking) or wait around for a rev or 2
(my
| If none of the features are that useful to you, then by all means stick
| with 4.7 or whatever we're up to when 5.0-release comes out. I'm sure
Well, I definitely plan to move to 5.x. The question is when. When it
will be ready for general use, and when I will be able to learn all the
new
When using PCMCIA SCSI, how is the device destroyed when the card is
unloaded, so that the device can be re-created when the card is re-inserted
and the filesystem re-mounted?
Jonathon
--
Microsoft complaining about the source license used by
Linux is like the event horizon calling the kettle
On Sat, Jun 23, 2001 at 02:54:29PM +0300, Peter Pentchev wrote:
| On Fri, Jun 22, 2001 at 06:39:09PM +0100, j mckitrick wrote:
|
| Here is the code for a scsi removable media drive. If this is to become a
| module, the cam/scsi attachment must be removed. I have tried calling
On Sat, Jun 23, 2001 at 10:38:53AM -0700, Matthew Jacob wrote:
|
| But the unit numbers can and do recycle.
So the question is then, how can i get it to do that?
Jonathon
--
Microsoft complaining about the source license used by
Linux is like the event horizon calling the kettle black.
To
Here is the code for a scsi removable media drive. If this is to become a
module, the cam/scsi attachment must be removed. I have tried calling
cam_sim_free() and xpt_bus_deregister() but when the module is reloaded, the
cam system assigns the next higher minor device number, and then crashes
On Fri, Jun 22, 2001 at 10:41:09AM -0700, Matthew Jacob wrote:
|
| Wrong list. Send this to -scsi
Yeah, i figured i would get this response. But at least it's a response.
:-)
The same post to -scsi went unanswered, so i thought i would try here. Oh,
well.
To Unsubscribe: send mail to [EMAIL
hi all,
i'm working on turning the zip driver and all the ppbus devices into
modules. So far, i have the vpo (zip driver) detaching, but i have problems
when i reattach.
In the initial attach() call, we allocate a tiny bit of memory for a device
controlling microsequence, and we call
| : How would you recommending fixing this, taken from the ex driver?
|
| By deleting it.
|
| Uh, what?
|
| Non PnP devices that can be autodetected should be autodetected.
|
| Relying on the user to wire down hints is silly.
|
| Probably they should provide an identify method to
The newbus routines use a certain amount of overhead, but once done, you
forget about it. In some device drivers, the probe methods often need to
try a variety of hardware ports. In the past, inb/outb was used, along with
an often hardcoded port address.
Does it make sense to call
| Typically, probe routines these days are invoked with a single set of I/O
| parameters to probe (and even this is only ISA devices).
|
| It's pretty rare to need to bit-bang to find a device these days anyway;
| you should probably be looking for PnP data or similar. This is what
| hints
| You manually set the correct I/O port in the hints file and then you
| don't have to check for each port between 0x200 and 0x3a0.
|
| Just bus_alloc_resource once and test for the card.
So without having the card for testing, i should just wrap the port access
calls into bus_xxx calls?
jcm
On Thu, May 24, 2001 at 08:06:58PM -0600, Warner Losh wrote:
| In message [EMAIL PROTECTED] j mckitrick writes:
| : I'd like to finalize the newbus work by changing inb()/outb() calls to
| : bus_space_write calls. Is there a device where this has been partially done
| : already? I'd like to see
One more question:
In the probe routines, the values of the hardware ports are changing from
one chipset to the next. Throughout the ppc driver, the regular macros are
used to access the parallel port control registers, but in the probe routine
it reverts to inb/outb, probably because it makes
| Yes, but it does make sense to do that. Some busses you cannot access
| the resources until they have been activated. pcmcia comes to mind :-).
ah, but of course. :-)
Well, then, let me know if my plan is acceptable:
I will newbussify all macros, and any inb/outb calls i find that are not
On Thu, May 24, 2001 at 11:38:15AM +0200, Alexander Langer wrote:
| Thus spake j mckitrick ([EMAIL PROTECTED]):
|
| Any devices using the ppbus will end up sharing the hardware port. If i want
| to access this resource info, should i store it in my local driver's softc
| structure
I'd like to finalize the newbus work by changing inb()/outb() calls to
bus_space_write calls. Is there a device where this has been partially done
already? I'd like to see the old and new styles, then i would fix the
vpo/imm zip driver first, since i know that code well. After that, i could
On Wed, May 23, 2001 at 07:04:15PM +0200, Alexander Langer wrote:
| Thus spake j mckitrick ([EMAIL PROTECTED]):
|
| I'd like to finalize the newbus work by changing inb()/outb() calls to
| bus_space_write calls. Is there a device where this has been partially done
| already? I'd like to see
Any devices using the ppbus will end up sharing the hardware port. If i want
to access this resource info, should i store it in my local driver's softc
structure, or extract it from the parent device (ppbus)?
jcm
--
I drank WHAT ?! - Socrates
To Unsubscribe: send mail to [EMAIL PROTECTED]
Hi all,
I had planned to buy 'Design and Implementation of the BSD 4.4 Operating
System' but I heard the rumor that there will be a revision out this summer
that will not only be updated, but will focus on FreeBSD. I don't want to
repeat any more of the rumor if it is untrue, but I was told if
Greets to everyone,
I'm new to hackers, but I'm trying to tackle a couple of bugs in the
parallel port zip driver under newbus/4.x. I was able to fix the big one
(nibble mode didn't work at all) so now I am trying to get PS2 mode working,
which is much faster on reads.
I have 2 questions:
1.
| Could you point a date (or date range) when that commit to CAM was? I'm
| vaguely familiar with it and more than willing to help.
I can *try*, but it was someone else who spotted the changes, and I can't
seem to contact him. But he also did not find a specific change. I can
give it a shot,
| I'll put this on my pile of things to and dig through the CAM changes to
| find it. There weren't that many in the past year.
I finally heard from the guy who noticed the change, and asked if he could
help localize it.
| I don't know much about the PS2 mode nor the parallel port driver
|
Hello all,
I am new to -hackers, and I have run into a very frustrating problem. I am
using standard printf statements for status info while debugging the
parallel port zip driver in PS2 mode. For a reason I have yet to discover,
my messages are no longer appearing consistently in my dmesg
Hi all,
there are two recent articles on newbus on daemonnews, and one at
people.freebsd.org/~asmodai by jeroen. Does anyone remember seeing any
others? I thought for sure i remembered seeing a article explaining the OO
design concepts behind newbus, particularly the use of soft_c, the local
Is there a document anywhere that explains the newbus function calls?
Technically, i'm supposed to be writing it ;-)
But i am trying to trace some calls and it gets pretty crazy sometimes. I'm
debugging the parallel port zip driver, and i'm not sure which functions are
the entry points. And
On Sun, May 21, 2000 at 12:02:53PM +0100, Nick Hibma wrote:
You can single step at boot time, by setting the flags in the loader.
None of this will be source level, correct? Will it at least have labels if
i use a debug kernel?
jm
--
I've used softice for debugging under windows, and i was wondering if gdb
offers similar capabilities. It seems the best way to debug the ECP
parallel port problem is to step through the code during the boot phase.
Can this be done, or is there too much timing-critical stuff going on then?
jm
Is there any ECP code anywhere besides the /usr/src/sys/dev/ppbus directory?
I'm trying to trak down why ECP doesn't work undder 4.0. So, far, i can't
find any significant differences, other than the newbus function calls.
Where does the ECP status get reported, and where is the ECP transfer
On Tue, May 16, 2000 at 12:44:26PM -0700, Mike Smith wrote:
Is there any ECP code anywhere besides the /usr/src/sys/dev/ppbus directory?
I'm trying to trak down why ECP doesn't work undder 4.0. So, far, i can't
find any significant differences, other than the newbus function calls.
Where
I just realized i think this machine may not have that part of the source
installed.
Also, the ppc code is even more complex than the ppbus stuff. I don't know
how much good i'll be able to do. Does anyone have any ideas on figuring
out why ECP is broken? Is it broken in -current as well?
jm
On Tue, May 16, 2000 at 01:33:34PM -0700, Mike Smith wrote:
Also, the ppc code is even more complex than the ppbus stuff. I don't know
how much good i'll be able to do. Does anyone have any ideas on figuring
out why ECP is broken? Is it broken in -current as well?
No ideas, no. You
I saw this link recently...
http://home.zonnet.nl/vanrein/badram/
Apparently, you make a floppy with the supplied image, boot with it to
find the bad RAM addresses, and then those addresses are passed on as a
kernel parameter once the patch is applied. Bad addresses will be excluded
from
On Thu, Apr 06, 2000 at 10:13:25AM -0700, Brooks Davis wrote:
On Thu, Apr 06, 2000 at 04:41:15PM +0100, J McKitrick wrote:
I saw this link recently...
http://home.zonnet.nl/vanrein/badram/
Apparently, you make a floppy with the supplied image, boot with it to
find the bad RAM
I had a nightmare problem with Linux filesystems. Yes, i'm just a newbie
recreational linux user. But i had installed mandrake 6.0, which
apparently had serious filesystem bugs that would corrupt data if the
cdrom was mounted during shutdown. I had to reinstall because of that,
and even after
37 matches
Mail list logo
