On Mon, Aug 4, 2014 at 11:18 PM, Nick Krause wrote:
> On Mon, Aug 4, 2014 at 9:33 PM, Nick Krause wrote:
>> On Mon, Aug 4, 2014 at 8:12 PM, Sarah Sharp
>> wrote:
>>> On Mon, Aug 04, 2014 at 07:11:07PM -0400, Nick Krause wrote:
On Mon, Aug 4, 2014 at 7:03 PM, Paul Zimmerman
wrote:
On Mon, Aug 4, 2014 at 9:33 PM, Nick Krause wrote:
> On Mon, Aug 4, 2014 at 8:12 PM, Sarah Sharp
> wrote:
>> On Mon, Aug 04, 2014 at 07:11:07PM -0400, Nick Krause wrote:
>>> On Mon, Aug 4, 2014 at 7:03 PM, Paul Zimmerman
>>> wrote:
>>> >> From: Nick Krause [mailto:xerofo...@gmail.com]
>>
>> [sni
On Mon, Aug 4, 2014 at 8:12 PM, Sarah Sharp
wrote:
> On Mon, Aug 04, 2014 at 07:11:07PM -0400, Nick Krause wrote:
>> On Mon, Aug 4, 2014 at 7:03 PM, Paul Zimmerman
>> wrote:
>> >> From: Nick Krause [mailto:xerofo...@gmail.com]
>
> [snip]
>
>> >> Paul ,
>> >> My computer is rather old now as of Sa
On Mon, Aug 04, 2014 at 07:11:07PM -0400, Nick Krause wrote:
> On Mon, Aug 4, 2014 at 7:03 PM, Paul Zimmerman
> wrote:
> >> From: Nick Krause [mailto:xerofo...@gmail.com]
[snip]
> >> Paul ,
> >> My computer is rather old now as of Sandy Bridge days, so I probably
> >> can't test the patch
> >> o
On Mon, Aug 4, 2014 at 7:03 PM, Paul Zimmerman
wrote:
>> From: Nick Krause [mailto:xerofo...@gmail.com]
>> Sent: Monday, August 04, 2014 3:50 PM
>>
>> On Mon, Aug 4, 2014 at 5:55 PM, Paul Zimmerman
>> wrote:
>> >> From: valdis.kletni...@vt.edu [mailto:valdis.kletni...@vt.edu]
>> >> Sent: Monday,
> From: Nick Krause [mailto:xerofo...@gmail.com]
> Sent: Monday, August 04, 2014 3:50 PM
>
> On Mon, Aug 4, 2014 at 5:55 PM, Paul Zimmerman
> wrote:
> >> From: valdis.kletni...@vt.edu [mailto:valdis.kletni...@vt.edu]
> >> Sent: Monday, August 04, 2014 1:28 PM
> >>
> >> On Mon, 04 Aug 2014 19:40:1
On Mon, Aug 4, 2014 at 5:55 PM, Paul Zimmerman
wrote:
>> From: valdis.kletni...@vt.edu [mailto:valdis.kletni...@vt.edu]
>> Sent: Monday, August 04, 2014 1:28 PM
>>
>> On Mon, 04 Aug 2014 19:40:15 -, Paul Zimmerman said:
>>
>> > Ah, you didn't read far enough down the page :)
>>
>> I'm willing
> From: valdis.kletni...@vt.edu [mailto:valdis.kletni...@vt.edu]
> Sent: Monday, August 04, 2014 1:28 PM
>
> On Mon, 04 Aug 2014 19:40:15 -, Paul Zimmerman said:
>
> > Ah, you didn't read far enough down the page :)
>
> I'm willing to bet a large pizza with everything but anchovies that
> ou
On Mon, 04 Aug 2014 19:40:15 -, Paul Zimmerman said:
> Ah, you didn't read far enough down the page :)
I'm willing to bet a large pizza with everything but anchovies that
out in the real world, a lot of implementors didn't read further either. :)
> So I have to believe there are a *lot* of s
> From: valdis.kletni...@vt.edu [mailto:valdis.kletni...@vt.edu]
> Sent: Monday, August 04, 2014 12:23 PM
>
> On Mon, 04 Aug 2014 19:07:53 -, Paul Zimmerman said:
>
> > Are you sure about that? Last I heard, xHCI debug support was a logo
> > requirement from Microsoft for Windows 8 and above,
On Mon, 04 Aug 2014 19:07:53 -, Paul Zimmerman said:
> Are you sure about that? Last I heard, xHCI debug support was a logo
> requirement from Microsoft for Windows 8 and above, so I would have
> thought that most vendors would have implemented it by now.
There's a lot of gear out in the real
> From: linux-usb-ow...@vger.kernel.org
> [mailto:linux-usb-ow...@vger.kernel.org] On Behalf Of Sarah Sharp
> Sent: Monday, August 04, 2014 9:47 AM
>
> Please Cc the new xHCI driver maintainer, Mathias Nyman. I'm officially
> retired from USB development and have moved onto other projects. :)
>
On Sat, Aug 02, 2014 at 12:47:59AM -0400, Nick Krause wrote:
> Hey Sharp,
Hi Krause,
Please Cc the new xHCI driver maintainer, Mathias Nyman. I'm officially
retired from USB development and have moved onto other projects. :)
> After reading around seems people want support for usb debugging in
On Mon, Aug 4, 2014 at 4:29 PM, Austin S Hemmelgarn
wrote:
> On 2014-08-04 10:21, Alan Stern wrote:
>> On Mon, 4 Aug 2014, Austin S Hemmelgarn wrote:
>>
>>> On 2014-08-02 09:48, Alan Stern wrote:
On Sat, 2 Aug 2014, Nick Krause wrote:
> Hey Sharp,
> After reading around seems peo
On 2014-08-04 10:21, Alan Stern wrote:
> On Mon, 4 Aug 2014, Austin S Hemmelgarn wrote:
>
>> On 2014-08-02 09:48, Alan Stern wrote:
>>> On Sat, 2 Aug 2014, Nick Krause wrote:
>>>
Hey Sharp,
After reading around seems people want support for usb debugging in
kgdb or other usb based s
On Mon, 4 Aug 2014, Austin S Hemmelgarn wrote:
> On 2014-08-02 09:48, Alan Stern wrote:
> > On Sat, 2 Aug 2014, Nick Krause wrote:
> >
> >> Hey Sharp,
> >> After reading around seems people want support for usb debugging in
> >> kgdb or other usb based solutions.
> >> If you and the other develop
On 2014-08-02 09:48, Alan Stern wrote:
> On Sat, 2 Aug 2014, Nick Krause wrote:
>
>> Hey Sharp,
>> After reading around seems people want support for usb debugging in
>> kgdb or other usb based solutions.
>> If you and the other developers are able to help me out a bit as I am
>> new I can definit
On Sat, Aug 2, 2014 at 9:48 AM, Alan Stern wrote:
> On Sat, 2 Aug 2014, Nick Krause wrote:
>
>> Hey Sharp,
>> After reading around seems people want support for usb debugging in
>> kgdb or other usb based solutions.
>> If you and the other developers are able to help me out a bit as I am
>> new I
On Sat, 2 Aug 2014, Nick Krause wrote:
> Hey Sharp,
> After reading around seems people want support for usb debugging in
> kgdb or other usb based solutions.
> If you and the other developers are able to help me out a bit as I am
> new I can definitively write this
> area of kgdb support.
Doesn'
On Mon, 2005-07-25 at 15:23 -0400, [EMAIL PROTECTED] wrote:
> I am using Red Hat sources, which has function open_kcore() hardcoded to
> return -EPERM always.
>
> Changing this function to the way it is defined in the public sources (as
> shown below) did the trick.
All these Red Hat / RHEL threa
I am using Red Hat sources, which has function open_kcore() hardcoded to
return -EPERM always.
Changing this function to the way it is defined in the public sources (as
shown below) did the trick.
open_kcore(struct inode * inode, struct file * filp)
{
return capable(CAP_SYS_RAWIO) ? 0 : -EPER
On 7/24/05, Jesper Juhl <[EMAIL PROTECTED]> wrote:
> On 7/24/05, UmaMaheswari Devi <[EMAIL PROTECTED]> wrote:
> > I am new to kernel hacking and am facing problems in trying to peek at the
> > runtime values of some kernel variables using gdb.
> >
> > I am issuing the gdb command as follows:
> >
On 7/24/05, UmaMaheswari Devi <[EMAIL PROTECTED]> wrote:
> I am new to kernel hacking and am facing problems in trying to peek at the
> runtime values of some kernel variables using gdb.
>
> I am issuing the gdb command as follows:
> gdb vmlinux /proc/kcore
> This displays the message
> /
Andrea Arcangeli wrote:
>
> Back in May I wrote a quite estensive documentation about all the
> possible/best ways to debug the Linux Kernel for a talk/tranining that I
> did in San Jose in May. I find now the time to clean it up and to upload
> since I think it could result useful to everybody d
Andrea,
You're a stud. This is great.
:-)
Jeff
Andrea Arcangeli wrote:
>
> Back in May I wrote a quite estensive documentation about all the
> possible/best ways to debug the Linux Kernel for a talk/tranining that I
> did in San Jose in May. I find now the time to clean it up and to upload
Elmer Joandi wrote:
>
> > understanding the
> > > underlying principles and the code.
>
> Speaking about that, I have been long time dreaming
> about following strict standard template for linux kernel functions:
> (macroplay intended)
> --
> INLINE(context,level,for_speed,
"Amit S. Kale" wrote:
>
> George Anzinger wrote:
> > I took a look at this and it looks very messy. The whole notion is that
> > the stack is available to put the call on and then proceed. The
> > question then is what does the stack look like after the call to the
> > inferior function which,
27 matches
Mail list logo
