Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Dump\s+driver\s+interface\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Dump\s+driver\s+interface\s*$/: 12 ]

Total 12 documents matching your query.

1. Dump driver interface (score: 1): Author: Suparna Bhattacharya <suparna@xxxxxxxxxx>; Date: Mon, 8 Oct 2001 14:23:03 -0500; Matt, To carry on some of the discussions you'd initiated about having a block device dump interface. A question that comes to mind when comparing the proposed interface with the AIX ddump interface,; /archives/lkcd/2001-10/msg00013.html (13,742 bytes)
2. Re: Dump driver interface (score: 1): Author: "Matt D. Robinson" <yakker@xxxxxxxxxxxxxx>; Date: Mon, 08 Oct 2001 23:46:42 -0700; Setting aside resources may be problematic, as the main developers will balk (I believe) at taking system resources for something you may never use. But then again, not everyone will use LKCD in the; /archives/lkcd/2001-10/msg00015.html (16,964 bytes)
3. Re: Dump driver interface (score: 1): Author: Suparna Bhattacharya <suparna@xxxxxxxxxx>; Date: Tue, 9 Oct 2001 12:06:20 -0500; Exactly ! That was the reason for trying to outline the tasks - so we can bring up common stuff into the generic dump functionality, providing more control & flexibility in the fray. So the write cal; /archives/lkcd/2001-10/msg00016.html (9,541 bytes)
4. Re: Dump driver interface (score: 1): Author: Castor Fu <castor@xxxxxxxxxxxx>; Date: Tue, 9 Oct 2001 10:46:53 -0700 (PDT); One thing that might be nice, (I'm still on the fence on this matter), is to structure the code so it could be standalone code outside of the linux kernel. This would imply factoring out the iteratio; /archives/lkcd/2001-10/msg00017.html (8,307 bytes)
5. Re: Dump driver interface (score: 1): Author: "Matt D. Robinson" <yakker@xxxxxxxxxxxxxx>; Date: Tue, 09 Oct 2001 16:16:57 -0700; In what sense? Right now, we're a module, but I suspect you aren't referring to this. Are you referring to something like LinuxBIOS? Just curious. We have briefly discussed something like this, along; /archives/lkcd/2001-10/msg00018.html (8,795 bytes)
6. Re: Dump driver interface (score: 1): Author: Castor Fu <castor@xxxxxxxxxxxx>; Date: Tue, 9 Oct 2001 16:22:54 -0700 (PDT); Well, not LinuxBIOS, but yes, from a custom BIOS. With things like the SMI interrupt one could potentially get at a pretty wedged system from a BIOS. Another factor to consider, (pardon my unfamiliar; /archives/lkcd/2001-10/msg00019.html (8,351 bytes)
7. Dump driver interface (score: 1): Author: Suparna Bhattacharya <suparna@xxxxxxxxxx>; Date: Mon, 8 Oct 2001 14:23:03 -0500; Matt, To carry on some of the discussions you'd initiated about having a block device dump interface. A question that comes to mind when comparing the proposed interface with the AIX ddump interface,; /archives/lkcd/2001-10/msg00073.html (13,898 bytes)
8. Re: Dump driver interface (score: 1): Author: "Matt D. Robinson" <yakker@xxxxxxxxxxxxxx>; Date: Mon, 08 Oct 2001 23:46:42 -0700; Setting aside resources may be problematic, as the main developers will balk (I believe) at taking system resources for something you may never use. But then again, not everyone will use LKCD in the; /archives/lkcd/2001-10/msg00075.html (17,048 bytes)
9. Re: Dump driver interface (score: 1): Author: Suparna Bhattacharya <suparna@xxxxxxxxxx>; Date: Tue, 9 Oct 2001 12:06:20 -0500; Exactly ! That was the reason for trying to outline the tasks - so we can bring up common stuff into the generic dump functionality, providing more control & flexibility in the fray. So the write cal; /archives/lkcd/2001-10/msg00076.html (9,717 bytes)
10. Re: Dump driver interface (score: 1): Author: Castor Fu <castor@xxxxxxxxxxxx>; Date: Tue, 9 Oct 2001 10:46:53 -0700 (PDT); One thing that might be nice, (I'm still on the fence on this matter), is to structure the code so it could be standalone code outside of the linux kernel. This would imply factoring out the iteratio; /archives/lkcd/2001-10/msg00077.html (8,335 bytes)
11. Re: Dump driver interface (score: 1): Author: "Matt D. Robinson" <yakker@xxxxxxxxxxxxxx>; Date: Tue, 09 Oct 2001 16:16:57 -0700; In what sense? Right now, we're a module, but I suspect you aren't referring to this. Are you referring to something like LinuxBIOS? Just curious. We have briefly discussed something like this, along; /archives/lkcd/2001-10/msg00078.html (8,871 bytes)
12. Re: Dump driver interface (score: 1): Author: Castor Fu <castor@xxxxxxxxxxxx>; Date: Tue, 9 Oct 2001 16:22:54 -0700 (PDT); Well, not LinuxBIOS, but yes, from a custom BIOS. With things like the SMI interrupt one could potentially get at a pretty wedged system from a BIOS. Another factor to consider, (pardon my unfamiliar; /archives/lkcd/2001-10/msg00079.html (8,376 bytes)

Current List: 1 - 12
Page: [1]