Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Steven J. Hill" <sjhill@realitydiluted.com>
To: durai <durai@isofttech.com>
Cc: uclinux-dev <uclinux-dev@uclinux.org>, mips <linux-mips@linux-mips.org>
Subject: Re: Network problem in mips
Date: Thu, 11 Dec 2003 10:25:01 -0500	[thread overview]
Message-ID: <3FD88C4D.6010700@realitydiluted.com> (raw)
In-Reply-To: <008f01c3bff7$252e3b40$0a05a8c0@DURAI>

durai wrote:
>
> I am working on a wireless lan driver in mips platform. When i 
> transmit/receive the data at 11mbps, it is working smoothly. when i 
> change the tx speed to 54mbps, the system crashes at schedule() 
> function. I am not able to trace from where the crash occurs. where 
> could be the problem?
>

Dear,

[ ] Troller
[*] Idiot
[*] Lamer
[ ] Waster of bandwidth
[ ] Evolutionary Dead End
[*] Clueless Newbie
[ ] AOLer
[ ] "Me-too"-er
[ ] Scientologist


You are being flamed because

[*] You did not provide kernel symbols for your kernel oops
[*] You crossposted
[ ] You are an AOLer
[ ] You posted in ALL CAPS
[ ] You posted in HTML
[ ] You are a troller
[ ] You quoted an entire message in your reply of 0 LINES
[ ] You requested warez
[ ] You flamed someone for a spelling error.
     [ ] ... and you misspelled something in the process
[*] You suck
[*] I just don't like you

To repent you must

[ ] Give up your AOL account
[ ] Go hide under a Bridge.  If you do not have a bridge, we can sell you
     one named Brooklyn
[ ] Go find a hose
[ ] Go to the top of the CN Tower and attempt to defy gravity
[*] Eat your modem
[*] See how long it takes to fall down the Grand Canyon
[*] Shove a Cinnabon into your computer.  Without replacing the case, ground
     yourself to the Power Supply and turn computer on

In closing, I would like to say

[ ] AOL sucks!
[ ] Never post again
[*] Would you like deep fried or extra crispy?
[*] Go back to your little Nintendo, assmunch.
[ ] CAPS LOCK!  It's on the left!
[ ] Die, spammer!
[*] Get a clue!
[ ] Go away!
[*] Learn to read mail archives

  reply	other threads:[~2003-12-11 15:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-11 14:57 Network problem in mips durai
2003-12-11 15:25 ` Steven J. Hill [this message]
2003-12-11 23:07   ` Alan Cox
2003-12-11 23:30     ` Ralf Baechle
2003-12-11 23:46       ` Maciej W. Rozycki
2003-12-13  1:10         ` Ralf Baechle
2003-12-12 15:19       ` [uClinux-dev] " Paul Mundt
2003-12-12 19:25       ` Alan Cox
2003-12-12  7:44   ` durai
2003-12-12 17:42     ` Steven J. Hill
2003-12-13  2:48     ` Ralf Baechle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3FD88C4D.6010700@realitydiluted.com \
    --to=sjhill@realitydiluted.com \
    --cc=durai@isofttech.com \
    --cc=linux-mips@linux-mips.org \
    --cc=uclinux-dev@uclinux.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox