RE: A question about /linux/driver/net/e100

This is a multi-part message in MIME format.

------=_NextPart_000_0013_01C35168.F375FB30
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi De Yu Liu!
Hi Scott Feldman!

De Yu Liu <[email protected]> wrote:
> Oliver Pitzeier <[email protected]> wrote:
> > > Greeting all:
> > > In /linux/driver/net/e100 directory of RH 9,
> > > there are several files like e100_config.c, e100_eeprom.c, e100_main.c,
> > > e100_phy.c, e100_proc.c, e100_test.c and etc.
> > > What's is the relationship between them?
> > > Please draw me a picture like flow chart?
> > > Thanks in advance.

> > The AXP mailing list is certainly not the right
> > place for such questions, but however... We get used to it...
> > Don't we?

> > I can't access my kernel-repository currently, but I take a guess:

[ ... ]

> Thanks a lot.

No problem... Was just a guess! :)

> I think you're right.

Not completely... I remembered, that e100_test.c is using other files (_config,
_phy, and maybe _proc). So e100_test.c is _NOT_ used by e100_main.c... Can be
wrong again... But I guess that's true now....

> But is any relationship between others except *main.c?

They do not have any relation-ship... All those files are included by
e100_main.c...

> What's the role for each file?

Every file has some specific functions... e100_config.c is for configuration
stuff. e100_eeprom.c is for reading and (maybe) writing the onboard EEPROM. The
e100_phy.c has something to do with the MII register stuff and is executed in
polled time... e100_proc.c takes care of /proc entries and so on... I guess
that's also right...

> I look at the manual and try to make a corresponding match between
> the topic in manual and each file under .../e100/ directory.

What manual?

> But i couldn't figure it out.

I hope, that I could help you! I believe, that Scott Feldman (the e100
maintainer) can help you MUCH more... Keep me posted CC: while discussing this
topic... :)

I attached my ascii-art and parts of my previous mail, so Scott can tell me,
that I'm completely wrong. :)

Best regards,
 Oliver

------=_NextPart_000_0013_01C35168.F375FB30
Content-Type: text/plain;
	name="e100.txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="e100.txt"

The AXP mailing list is certainly not the right place for such =
questions, but however... We get used to it... Don't we?

I can't access my kernel-repository currently, but I take a guess:

---------------              -------------
|e100_config.c|------------->|e100_main.c|
---------------              -------------
                              ^ ^ ^ ^
                              | | | |
                              | | | --------------
                              | | |              |
---------------               | | -------------  |
|e100_eeprom.c|---------------- | |e100_proc.c|  |
---------------                 | -------------  |
                                |                |
------------                    | -------------  |
|e100_phy.c|--------------------- |e100_test.c|---
------------                      -------------

That's maybe completely wrong, but *main.c normaly is the glue between =
everything else.

------=_NextPart_000_0013_01C35168.F375FB30--