From: Annamalai Prakash <prakash@comodo.com>
To: lartc@vger.kernel.org
Subject: [LARTC] arm Linux 2.4.19-rmk7-ds3 with Traffic shaping and Routing.
Date: Fri, 07 Jan 2005 10:27:43 +0000 [thread overview]
Message-ID: <200501071545.49002.prakash@comodo.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I am very newbie to this group. I am working on ixdp425 embedded
Board. I have brought up board with linux 2.4.19-rmk7-ds3 kernel with Qos
support. Now i want to do traffic control (tc) on my board. Is there any
patches available for this kernel and also application. I dont know which
version of iproute2 is compitable one with this. i m planning to use
iproute2-1.2.7a. Please guide me ... i m trying to implement this from last
week...
- --
Thanks & Regards
K.Annamalai Prakash
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQFB3mFSk8m0kb/vZlYRAloYAKCaIxi8qt5nCcrnAKPsAl3sJbnHmgCeNew/
77RRJgIp4szEsZ45jGykpo0ëwj
-----END PGP SIGNATURE-----
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2005-01-07 10:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200501071545.49002.prakash@comodo.com \
--to=prakash@comodo.com \
--cc=lartc@vger.kernel.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