Brett Favre told SI.com’s Peter King that he wasn’t sure if he was going to be able to play against the Packers yesterday because of a groin injury. Favre claims he suffered the injury last week in practice and then re-aggravated it in pregame warm-ups.

“I told T-Jack [backup Tarvaris Jackson] and [offensive coordinator] Darrell Bevell I may not be able to do it,” he said. “I didn’t know if I’d be able to drop back very well. After I aggravated it, there was no way I was going to be able to move around in the pocket very much. We never called one bootleg the whole game. But we made it through OK.”

And now, I wondered, how was the groin four hours and a lot of lost adrenalin later?

“It’s throbbing right now,” he said.

Oh…come…on. Look, I don’t doubt that Favre injured himself in practice (he is 60 years old after all) and then re-injured himself during pregame warm-ups. I also don’t doubt that he told Jackson and Bevell that he was hurt and might not be able to play.

But I don’t buy for a minute that he was going to hold himself out. He wasn’t going to allow a groin injury to get in the way of beating the Packers at Lambeau and if anything, I’m willing to bet that he wanted people to know that he was hurt just so he could build the moment up even more.

Some are going to look at this as the “gritty” Brett playing through pain; I’m sure ESPN is already salivating thinking about the story. But I think this guy has a lot of people fooled.

Maybe I’m being to cynical and over thinking this, but it’s Brett’s comments that bug me the most. If King asked him how he was feeling and Brett said, “Well Pistol Pete, I’m a little sore because of a groin injury I suffered last week,” then I wouldn’t question him because the comment would have been more fly-by.

But no, Brett made damn sure to note that he might not have been able to play. To me, that’s just another prima donna move by one of the more underrated prima donna athletes of all-time.

The Vikings’ 38-26 win over the Packers wasn’t even an hour old yet and I got an e-mail from my partner in crime here at The Scores Report, John Pauslen, who happens to be a huge Green Bay fan and is/was an active Brett Favre supporter.

I won’t share what John wrote in case there are women and children reading, but he wasn’t kind to Brett. And I can’t imagine that John is the only one who feels angry with Favre after what transpired on Sunday.

Brett walked into Lambeau Field, a place where he was known for being a legend, a hero and an icon, and essentially burned the place down. He completed 17-of-28 passes for 244 yards and four touchdowns, while also spending most of the game pumping his fists wildly in celebration of his accomplishments.

Many people still want to blame Ted Thompson for why Favre currently wears purple and white. But the fact of the matter is that there are 32 teams in the NFL and he wanted to be a Viking. If he just wanted to play football, he could have returned to the Jets. Hell, if he wanted to play football, he could have returned to the Packers two years ago because they said yes to him twice. It was the one “no” that has fans blaming Thompson, yet they should blame Favre for his indecisiveness and his desire to play in Minnesota before blaming the GM that eventually committed to Aaron Rodgers and decided to move forward.

I hope that Brett is satisfied with the outcome from today, because while he once again got his revenge on Thompson and the Packers, he also torched a lot of loyal Green Bay fans in the process. There will always be people that player worship and will root for Favre no matter what color jersey he wears, but there no doubt are many who watched the game today and said, “You know what? To hell with Brett Favre.”

The funny thing is, Brett’s true fans will always be in Green Bay. Unless he helps the Vikings win a Super Bowl, Minnesota fans will forget about him the moment he’s done playing for them and you’re kidding yourself if you think otherwise. So while he may feel good about the way things have transpired so far this season, he’s hurting his legacy in the long run by accomplishing exactly what he wanted in beating the Packers.

Was it worth it, Brett?

If the Ravens were going to knock off the undefeated Broncos on Sunday, they would need their defense would have to step up and play inspired.

Baltimore has struggled defensively the past couple weeks, but held Denver to only one score in a 30-7 rout in Week 8. The Raven defense harassed Broncos’ quarterback Kyle Orton for much of the contest and limited him to 23-of-37 passing for 152 yards and no touchdowns.

The Ravens’ secondary has struggled all season, but was great today. Part of their success came from Orton’s inability to stretch the field vertically, but credit Baltimore’s defensive backs for not allowing the big play. They also benefited from a relentless pass rush, which produced two sacks and five QB hits.

If the Ravens are going to make the playoffs this season, how they played Sunday is how they’ll have to play every week. They don’t have the defensive talent like they had in years past, so perfect execution is a must and that’s how they won today. Plus, while he didn’t set the stat sheet on fire, quarterback Joe Flacco was efficient and kept the chains moving all game.

As for the Broncos, this loss will serve Josh McDaniels’ squad well. Good teams learn more from losses than they do wins, so now we’ll see what McDaniels and his coaching staff is made of. The Broncos host the Steelers (who will be fresh coming off their bye) next week on Monday Night Football and if they can produce a win, it would go a long way in proving that McDaniels and his crew can make adjustments when their team needs them.

Following the Browns’ ugly 30-6 loss to the Bears on Sunday, running back Jamal Lewis said that he plans to retire after the season.

While he claims it wasn’t just a statement made in the heat of the moment, nobody would blame Lewis if it were. Lewis is 30, has seen his play drop quite a bit this year and he’s stuck on a morbid franchise. So why stick around?

I honestly don’t know how the Browns have won a game this year. Their defense is bad, but it pails in comparison to how atrocious Derek Anderson and the offense is, which turned the ball over five times on Sunday. Chicago’s secondary has been shredded at times this season, yet Anderson found a way to only complete 6-of-17 pass attempts for a measly 76 yards. Oh, and he also threw two interceptions and fumbled once.

I’m sure someone will raise the question of whether or not Brady Quinn should resume the starting spot over Anderson next week. But Quinn has already shown that he’s just as incapable of running the offense as Anderson is, so does it really matter? If I were a Cleveland fan (and I just threw up a little at the mere thought of that), I’d rather see Brett Ratliff given a chance to start before Quinn is given a second opportunity.

About the only reason to watch the Browns these days is to see whether or not defensive coordinator Rob Ryan will get in a fight with anyone on the sidelines. He and Jay Cutler went at it (verbally, of course) on Sunday and it was the only entertainment Cleveland provided all day.

With their 31-10 win over the Bills in Week 8, the Texans won their third straight game to improve to 5-3 on the season. But as ESPN’s Adam Schefter reports, Houston lost tight end Owen Daniels for the season due to a knee injury.

Daniels suffered the injury on a play in the first quarter of Sunday’s win. He racked up 39 receptions, 497 yards and five touchdowns coming into Week 8 and was emerging as one of the NFL’s best tight ends, if not the best.

Joel Dressen and rookie James Casey will try to fill the void left by Daniels in Houston’s offense. Casey caught two passes for 14 yards on Sunday, but won’t be nearly as effective as Daniels was for quarterback Matt Schaub.

Although Daniels’ injury certainly puts a damper on things, the Texans have to love heading into the second half with a winning record. But next week is huge, as they play in Indianapolis before taking their bye in Week 10. After their bye, Houston has winnable games against the Titans, Jaguars, Seahawks and Rams, although they do play the undefeated Colts twice, as well as the Dolphins and Patriots.

According to a report by the Kansas City Star, the Chiefs and troubled running back Larry Johnson are working on some kind of settlement that would decide LJ’s future with the team.

Asked whether that settlement would involve a separation from the team, (Johnson’s agent) Schaffer said: “Not necessarily.”

Schaffer said Johnson’s side is working on an appeal of the two-week suspension the team handed down Wednesday for detrimental conduct. Schaffer said Wednesday night that he hoped an appeal would be filed early Thursday, and it’s possible that settlement talks could delay that appeal.

Johnson would lose more than $600,000 if he serves the full two-week suspension. He also could face further punishment from the league and the Chiefs when this suspension expires Nov. 9.

This situation seems a little ridiculous. Johnson was out of line, the Chiefs suspended him and will decide his future with the team over the course of the next two weeks. So what is there to “settle?”

There’s a good chance that Johnson will never play another down with the Chiefs, so maybe the team is trying to work out a deal where LJ gets to keep part of his contract if he just goes away. Then again, there have been reports that the Chiefs don’t want to outright release him because then it provokes other players to act up if they want to get out of town. So I don’t know what to think at this point.

We’ll see what comes out of this “settlement.”

For the past couple days, I’ve been racking my brain trying to figure out why in the world the Panthers would stick with Jake Delhomme at quarterback.

To say that Delhomme has struggled this year would be a gross understatement. He is 2-4 as a starter, is leading the league in interceptions and has somehow found a way to make explosive receiver Steve Smith non-existent. So why stick with him instead of giving A.J. Feeley or Matt Moore an opportunity?

One reason is because the Panthers have so much money invested in Delhomme after they signed him to a five-year, $42.5 million extension in April. They thought Delhomme would shake off his brutal performance in last year’s playoffs and at the very least, be able to turn around and hand the ball off to DeAngelo Williams and Jonathan Stewart.

But Delhomme has been a disaster thus far and head coach John Fox is taking a huge risk in sticking with him. If Delhomme continues to struggle and Fox doesn’t make a move, then he’s basically saying to upper management that he can’t evaluate his own players Neither Feeley nor Moore would come in and light the world on fire, but as long as they didn’t turn the ball over they’d be more efficient than Delhomme.

Fox better hope Delhomme turns things around or else they both could be gone at the end of the year. The Panthers have been a model organization for inconsistency under Fox and I highly doubt management would stick with a head coach that can’t make a change when one is needed. Fox is essentially putting all his eggs in the Jake Delhomme basket and that’s a risky endeavor to say the least.

Following the Chiefs’ embarrassing loss to the Chargers on Sunday, running back Larry Johnson took a couple verbal swipes at head coach Todd Haley via his Twitter page, then proceeded to use a homophobic slur to degrade another Twitter user.

Here are LJ’s tweets (from Yahoo! Sports):

• “my father got more creditentials than most of these pro coaches. … google my father!!!!!!!”

• “My father played for the coach from “rememeber the titans”. Our coach played golf. My father played for redskins briefley. Our coach. Nuthn”

Following those messages, an exchange appeared between Johnson’s account and another Twitter user, in which the other user made a reference to an incident in which Johnson pled guilty to disturbing the peace after allegedly spitting into the face of a female patron at a nightclub. A message on Johnson’s account referred to the other Twitter user’s profile picture with a homophobic slur, calling it a “[expletive] pic” and called the user a “Christopher street boy.” Christopher Street is a well-known New York City street which became famous as a symbol for the city’s gay-pride movement.

The message posted in Johnson’s account containing the homophobic slur read:

• “think bout a clever diss then that wit ur [expletive] pic. Christopher street boy. Is what us east coast cats call u.”

The final message of the night on Johnson’s account read:

• “Make me regret it. Lmao. U don’t stop my checks. Lmao. So “tweet” away.”

Johnson’s agent tried to put out the fire claiming that Johnson was just trying to pump his father up and didn’t mean to degrade Haley. But it’s pretty clear by Johnson’s tweets that he was taking a shot at his head coach.

This isn’t the first time that Johnson has gotten into a controversial situation off the field. He has had four arrests for various degrees of battery since the Chiefs drafted him in 2003, including an incident in which he spat in the face of a female at a nightclub. That incident cost him a one-game suspension.

Outside of a potential cap hit (which would be in excess of over $8 million), what’s stopping GM Scott Pioli from dumping Johnson now? LJ turns 30 in November, is averaging a career-worst 2.7 yards per carry and he continues to be a distraction. I realize he has been on his best behavior under the new regime up until this point, but this Twitter situation seems like another one of his attempts to get traded. The Chiefs are trying to move in a new direction under Haley and Pioli and they can’t do it if everyone isn’t on the same page.

If Johnson doesn’t fit into their long-term plans, then KC should cut bait and move on. Every year teams find running back gems in the draft and Pioli is one of the best player evaluators in the NFL. They could easily find a more productive running back and one that has less baggage.

Again, the cap hit would be tough for the Chiefs to swallow, but Johnson hasn’t done squat since he signed his new contract a couple years ago. The positives of cutting LJ seem to outweigh the negatives.

Rev. Al Sharpton is upset with columnist Steve Serby of the New York Post about his column on Monday about Giants’ wideout Plaxico Burress.

Post columnist Steve Serby began his column in Monday’s editions with “Good for Tom Coughlin. Good for Coughlin for tightening the noose around Plaxico Burress.”

Burress has been fined and benched by the Giants for infractions including tardiness and missing practices. On Saturday, the wide receiver skipped a treatment for his neck, and was benched during the first quarter of the Giants’ win in Pittsburgh Sunday.

In criticizing Burress, Serby used a racially loaded and offensive term, Sharpton told the Daily News. “To make such a blatant racist statement about an African-American football player with a neck injury is completely unacceptable,” Sharpton said. “Clearly, the racial connotation is very disturbing. … This is the verbal reflection of a hanging noose.”

Sharpton said that if the Post did not acknowledge that the column was offensive, he would further highlight the issue but he did not specify what steps he would take. “They have to act swiftly,” Sharpton said. “If we don’t see action, I will lay out exactly what that is … we would like to talk to someone there about whether it was the writer or editor who let this in.”

Why any writer would even hint at anything that could be construed as racist is beyond me. And for an editor at the Post to not have the wherewithal to see that what Serby wrote could potentially be a problem is unconceivable, too.

But my understanding of the word “racism” is to have hatred towards another person because of their skin color. Now I don’t know Serby personally, but it’s probably safe to say that he doesn’t hate Plaxico Burress because of his skin color. He used an incredibly poor choice of words (seriously, there are millions of words in the English language and you go with noose?), but what he wrote is being taken out of context.

That said, the power of words can be incredibly damaging and Serby was flat out insensitive (and shortsighted for that matter). People should use their brains over their emotions to decipher what he meant, but still, I completely understand why Sharpton and others would be upset over this.

Apparently Eli Manning needs to do a better job of covering his mouth in the huddle. During the Giants’ 21-14 win over the Steelers on Sunday, Pittsburgh players knew what play New York was going to run when they stopped Brandon Jacobs short of the goal line in the first half because Manning accidentally tipped the off.

Defensive end Brett Keisel overheard Manning mouthing the play call and lined up the defense before Jacobs was stopped inches short of the goal line on the fourth-and-1 play early in the second quarter.

The goal-line stand — Jacobs failed on three successive plays to get in from the 1 — temporarily preserved Pittsburgh’s 7-3 lead.

“I was watching Eli’s lips the whole time and I saw him say, ‘32,’ so I went over and tried to tell everyone, ‘It’s right here,’ and we stopped it,” Keisel said. “That was a big play in the game.”
Asked if he heard Manning yell out the play call, Keisel said, “Yeah.”

Actually Brett, the big play in the game was when your long snapper snapped the ball over your punter’s head for a safety that tied the game at 14-14 in the second half. Then the bigger play was when you and your teammates allowed Manning to march up the field for a game-winning touchdown.

Your play was the big play in the first half. The big play of the game was the touchdown that allowed the Giants to win the game.