headers
Ryos Suzuki | 4 Dec 2004 10:02

socket.cxx

Hi all,

I read io/fileio/current/src/socket.cxx.
There is cyg_nstab_init in this file.but I cannot find its 
caller.
if I selected net/tcpip as protocol stack,
cyg_nstab_init call bsd_init in sockio.cxx.
however now bsd_init is nothing to do.
also I read sockio.c. There is NSTAB_ENTRY in the file.
however it has syncmode which is zero. so, it seems that no one 
lock in each socket function, socket, accept, listen and etc.
additionally read and write function are not locked, when they  
are used as network method.

in my opinion,
1) cyg_nstab_init must be called in somewhere.
2) NSTAB_ENTRY's syncmode isCYG_SYNCMODE_SOCK_FILE | CYG_
SYNCMODE_SOCK_NETSTACK
but in this case, network performance will be down by lock 
function. Each file descriptors should have different instances 
of lock.
3) read/write functions should be locked in socket use. 

How do you think?
I need guru's opinion.

Thank you,

--
Ryos Suzuki
(Continue reading)

Permalink | Reply | 0 comments |
headers
Vlasios Tsiatsis | 8 Dec 2004 01:54
Picon
Favicon

Question about 802.11 WLAN on eCos

Hi everyone, 
i have seen that there was a great interest in WLAN on
eCos. I am also interested in getting PCMCIA 802.11
support on  an eCos platform so i have s few
questions:
How easy is it to write an 802.11  driver or port some
other driver to eCos ? Has anyone started doing that ?
Any useful pointers would be appreciated.

thanks, 
vlassis

	
		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - You care about security. So do we. 
http://promotions.yahoo.com/new_mail
Permalink | Reply | 4 comments |
headers
Weqaar Janjua | 8 Dec 2004 05:13
Picon
Favicon

Re: Question about 802.11 WLAN on eCos

Read my posts on this list, subject "WLAN on eCos
(HW/SW design)".
-Weqaar Janjua

--- Vlasios Tsiatsis <vlasios <at> yahoo.com> wrote:

> Hi everyone, 
> i have seen that there was a great interest in WLAN
> on
> eCos. I am also interested in getting PCMCIA 802.11
> support on  an eCos platform so i have s few
> questions:
> How easy is it to write an 802.11  driver or port
> some
> other driver to eCos ? Has anyone started doing that
> ?
> Any useful pointers would be appreciated.
> 
> thanks, 
> vlassis
> 
> 
> 
> 	
> 		
> __________________________________ 
> Do you Yahoo!? 
> Yahoo! Mail - You care about security. So do we. 
> http://promotions.yahoo.com/new_mail
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Srivatsan | 8 Dec 2004 05:53

Redhat booting Linux - newbie question


Hi all,

     I am a newbie to Redhat and am considering some pointers to the
following questions.

    1) I tried to boot Linux using Redhat on a Rattler board. The board
I am having is a Rattler board (MPC8280) but the Linux kernel I am
having is a kernel for MPC8260ads board (Please don't ask me to change
the kernel for Rattler board). I build the kernel with initial ramdisk
and download the kernel onto the target (rattler board) at the address
0x00400000.[This is the address which is given in mkimage command]. The
kernel build is zImage.initrd.elf .

       But when I tried to give a <go 0x00400000> redboot starts
printing some junk for every key pressed on the keyboard [I feel that
the control is not transferred to the Linux Kernel but is still in the
Redboot or redboot is throwing some exception]. Please give me guidance
on booting the Linux Kernel with using Redboot.

2) Can anyone give me pointers on how much time Redboot takes to boot a
Linux Kernel (redboot boot + decompression]?

With Best Regards,
C.R.Srivatsan   

********************************DISCLAIMER**********************************

This e-mail and any attachment is for authorised use by the intended
recipient(s) only. It may contain proprietary material, confidential
(Continue reading)

Permalink | Reply | 2 comments |
headers
Weqaar Janjua | 8 Dec 2004 07:07
Picon
Favicon

Re: Redhat booting Linux - newbie question

MPC8280 has an onboard redBoot monitor which does
support linux booting but the compressed zImage is
loaded at the specified address location and will be
decompressed and run from a different location
depending on the available memory in RAM, for this you
need to convert the kernel image that you built into
an S-record file so you don't need to specify an
address when you boot. Also there might be interrupt
layout differences between MPC8280 and MPC8260ads, so
make sure all interrupts can be disabled. Which
filesystem are u using on flash, jffs2?
--------------------------------------
Weqaar Janjua
Senior, Computer Systems
Arizona State University - Polytechnic
--------------------------------------

--- Srivatsan <srivatsan <at> deccanetworld.com> wrote:

> 
> 
> Hi all,
> 
>      I am a newbie to Redhat and am considering some
> pointers to the
> following questions.
> 
>     1) I tried to boot Linux using Redhat on a
> Rattler board. The board
> I am having is a Rattler board (MPC8280) but the
(Continue reading)

Permalink | Reply | 1 comment |
headers
Neundorf, Alexander | 8 Dec 2004 08:35

AW: Question about 802.11 WLAN on eCos


> Von: ecos-devel-owner <at> sources.redhat.com
> 
> Hi everyone, 
> i have seen that there was a great interest in WLAN on
> eCos. I am also interested in getting PCMCIA 802.11
> support on  an eCos platform so i have s few
> questions:
> How easy is it to write an 802.11  driver or port some
> other driver to eCos ? Has anyone started doing that ?
> Any useful pointers would be appreciated.
> 
> thanks, 
> vlassis

We're also seriously interested in WLAN support for ecos, but haven't started yet.

Bye
Alex
Permalink | Reply | 0 comments |
headers
Srivatsan | 8 Dec 2004 09:52

RE: Redhat booting Linux - newbie question

Thanks Weqaar.

1) I have tried the Srecord part. I tried building the Srecord image but
it 
   is hanging the whole board. Nothing is displayed on the console, I
feel 
   there could be some porting issues or it could be that my building 
   steps are not proper or might be the board in my hand isn't working 
   properly. 

2) The kernel is configured for the following:

    a) Platform support is for ADS8260
    b) RAM Disk support and default ram disk size is 8192
    c) Initial ram disk support
    d) Support for console on virtual terminal
    e) standard/generic (8250/16550 and compatible UARTs)
    f) Support for console on serial port
    g) Ext3 journaling file system support.
    h) /proc file system support
    i) Enable SCC console
    j) Zlib decompression support
    k) Include KGDB support

3) I do a make dep, make zImage.initrd 
   for converting the kernel into a srec image I do 
         ppc_82xx-objcopy -O srec zImage.initrd

4) Anybody can share a working kernel for the Rattler board so that I
can
(Continue reading)

Permalink | Reply | 0 comments |
headers
Frank Pagliughi | 8 Dec 2004 19:37
Picon

Cirrus EP93xx chips

Does anyone know if Cirrus submitted their eCos port for the EP93xx ARM
chips to the repository? I've been fooling around with the TS-7200
(Technological Systems) board that uses the chip, but it has a partial
implentation of eCos, which I started to finish up, then Cirrus released an
updated port. Ugh. I'm being forked to death.
Permalink | Reply | 1 comment |
headers
Gary Thomas | 8 Dec 2004 20:00
Favicon

Re: Cirrus EP93xx chips

On Wed, 2004-12-08 at 11:37, Frank Pagliughi wrote:
> Does anyone know if Cirrus submitted their eCos port for the EP93xx ARM
> chips to the repository? I've been fooling around with the TS-7200
> (Technological Systems) board that uses the chip, but it has a partial
> implentation of eCos, which I started to finish up, then Cirrus released an
> updated port. Ugh. I'm being forked to death.

No, they have not.

This was recently discussed - try searching the various eCos archives
for the details.  Bottom line - they've not contributed and we think it
would be great if their customers (like yourself) could convince them
to do so.

Good luck.

--

-- 
Gary Thomas <gary <at> mlbassoc.com>
MLB Associates
Permalink | Reply | 0 comments |
headers
liberty | 15 Dec 2004 10:38

RFC: extending (reserved)

I'm requesting comments on extending CYGOPT_REDBOOT_FIS_RESERVED_BASE. As
it now stands, it reserves a generic portion of the flash. I'd like to
extend it and add the infrastructure to have multiple descriptive areas
reserved, such as "bootrom", "OS", etc..all machine specific.

I have two goals in mind:

1) multiple fis entries for reserved areas for a board, enjoying the
protection mechanism that "reserved" and "RedBoot" enjoy

2) simplify board ports to Linux.

On point 1, our platform needs guaranteed space for our BootROM and jffs2
image. An fis list shows them globbed together rather non-descriptively
with

(reserved)  0x60000000   0x60000000 0x00620000 0x0...
RedBoot     0x60620000   0x60620000 0x00040000 0x0...
etc. etc

I'd like to see them as
bootrom     0x60000000   0x60000000 0x00020000 0x0...
jffs2       0x60020000   0x60020000 0x00600000 0x0..
RedBoot     0x60620000   0x60620000 0x00040000 0x0..

this leads to point 2. We now have to create special
linux/drivers/mtd/maps files for our boards, though the physmap.c file
should work. Unfortuantely, we can't get access to the jffs2 image or the
bootrom section. I'd rather just let physmap.c pick up the various
partitions by reading the redboot fis entries.
(Continue reading)

Permalink | Reply | 4 comments |

Gmane