No, The OSI model is a model that is used for any data sent or recieved on the network, through any protocol, or any medium (ethernet, token ring, FDDI, wireless, ATM, etc). What you were probably looking at is the TCP/IP model, which is almost identical to the OSI model, but has a few sections that are fused together, and/or renamed.
In theory it would be easier to learn about hardware, like how a switch works and how a hub works, and objectively think, it's sending electrical signals across that are converted into bits.
However, once you start looking at routers or firewalls, or layer3 switches, then you'll have to know the OSI model. The OSI model is made to be easy to understand... Here's a brief intro, that covers almot everything you need to know about it:
The OSI Model (yes, it starts at 7)
7- Application Layer = Your programs which use the internet: Web broser/Email
6- Presentation Layer = Encoding/Encryption--to speek a common language
5- Session Layer = keep communication lines open, keep track of who your talking to
4- Transport Layer = tracking, making sure the data gets there
3- Network Layer = protocol area, eg. IP, protcol addressing (IP Address), Packet
2- Data Link Layer = the NIC, physical addressing, framing
1- Physical Layer = the medium, eg. etherenet, where electrical signals are sent across the network.
Here's how it's used:
=> to send something, you start at layer 7, and work your way down to where your comptuer sends the bits across the network.
=> to recieve something, you get the bits at layer1, and work your way up to the application that's waiting for the data
To troubleshoot a problem, work from layer1 upwards. 95% of your problems will be layer1 (physical problems), then test the NIC, then the protcols, etc.
A hub is a layer1 device, it just repeats everything it hears to everyone.
A switch is generally a layer2 device, it checks the MAC address, and then decides where to forward the frames to.
A layer 3 switch, or a router will read the Layer 3 IP addresses (or IPX or whatever protocol addressing you are using), and make decisions that way. The farther up the OSI model you go, the longer it takes.